#1102651 drkonqi: tries to launch multiple times per second and fails

Package:
drkonqi
Source:
drkonqi
Description:
Crash handler for Qt applications
Submitter:
Christian Britz
Date:
2025-08-10 20:07:02 UTC
Severity:
normal
#1102651#5
Date:
2025-04-11 13:13:17 UTC
From:
To:
Dear Maintainer,

on a fresh trixie install with kde plasma and all updates applied, I get the
following messages in system journal multiple times every second. It pauses
then for a while and starts again to happen.

[...]
Apr 11 15:09:32 Amiga5000 systemd[1972]: drkonqi-coredump-launcher.socket -
Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an
unmet condition check (ConditionUser=!@system).
Apr 11 15:09:32 Amiga5000 systemd[1972]: drkonqi-coredump-launcher.socket -
Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an
unmet condition check (ConditionUser=!@system).
Apr 11 15:09:32 Amiga5000 systemd[1972]: drkonqi-coredump-launcher.socket -
Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an
unmet condition check (ConditionUser=!@system).
Apr 11 15:09:32 Amiga5000 systemd[1972]: drkonqi-coredump-launcher.socket: Unit
needs to be started because active unit sockets.target upholds it, but not
starting since we tried this too often recently. Will retry later.
Apr 11 15:09:42 Amiga5000 systemd[1972]: drkonqi-coredump-launcher.socket -
Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an
unmet condition check (ConditionUser=!@system).
[...]

Regards,
Christian
#1102651#10
Date:
2025-04-28 00:54:33 UTC
From:
To:
Dear Maintainer,

I also just noticed this as it is causing unexpected disk IO. Same story for
me:

systemd[36958]: drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for
a systemd-coredump crash was skipped because of an unmet condition check
(ConditionUser=!@system).

My Trixie install did not originally do this. I see the first entry appears on
Apr 08 and I update my system regularly so something would have changed to
cause this around then. There are 303,785 entries in the journal for this since
it started to today, Apr 27.
#1102651#15
Date:
2025-04-28 01:02:18 UTC
From:
To:
I forgot to mention that executing

sudo systemctl --global disable drkonqi-coredump-launcher.socket
systemctl --user stop drkonqi-coredump-launcher.socket

as my user looks to stop the noisy log entries though I don't know what
ramifications may come from this. YMMV but I hope it helps someone else.
#1102651#20
Date:
2025-05-03 05:08:30 UTC
From:
To:
https://bugs.kde.org/show_bug.cgi?id=502960

Here's the KDE bug report about this.

https://discuss.kde.org/t/drkonqi-spams-journal-with-unmet-condition-check/
33007

Here's discussion about it on the KDE forum, it happens in the SUSE
development branch too.
#1102651#25
Date:
2025-05-23 09:38:41 UTC
From:
To:
My log is also spammed by these messages. It appears that the only
workaround so far is to disable the condition check in
'/usr/lib/systemd/user/drkonqi-coredump-launcher.socket' file.


Regards,

Rajko
#1102651#34
Date:
2025-07-23 15:02:58 UTC
From:
To:
Dear Maintainer,

I did a fresh Trixie installation yesterday using the RC2 netinst iso and then installed the KDE-Plasma desktop environment with "apt install kde-plasma-desktop".

After a reboot my journal gets flooded with the same messages, as other users already reported.

I am looking at the commit that introduced the ConditionUser=!@system check that seems to be the reason for those journal messages: https://invent.kde.org/plasma/drkonqi/-/commit/7dca985d21d76a98b4d39196404060c928afb9f4

To me the commit message sounds like running drkonqi as root is not supported.

Executing
"systemctl --global disable drkonqi-coredump-launcher.socket" as root and
"systemctl --user enable drkonqi-coredump-launcher.socket" as my user
and rebooting once again seems to fix it.

But I am kindly asking if there would be a way for you as the maintainer to fix it in the package. Because, if I understand it correctly, everybody who installs the KDE-Plasma desktop environment would have this issue because plasma-workspace depends on drkonqi.

I would appreciate if it could be fixed before the official release of Trixie.

Thank you very much in advance and have a nice day!
#1102651#39
Date:
2025-07-26 11:00:08 UTC
From:
To:
Executing the command

	systemctl --user mask drkonqi-coredump-launcher.socket

as root is probably a better work-around than what I mentioned in my previous message.

I am still concerned though that a lot of people will install KDE Plasma and will get their journals spammed - unless they manually mask the unit.

Is there really nothing we can do about this? :/
#1102651#44
Date:
2025-08-10 20:05:34 UTC
From:
To:
Package: drkonqi
Version: 5.27.5-2
Followup-For: Bug #1102651

I guess not. Thanks to everybody that tried.  I'm not sure which hack to try first.  Did anybody ping the
systemd guy?  Biebel?  Buler? Beuler? Beuller?

L8r,
bw