dpkg --search drkonqi-coredump-launcher.socket
drkonqi: /usr/lib/systemd/user/sockets.target.wants/drkonqi-coredump-launcher.socket
drkonqi: /usr/lib/systemd/user/drkonqi-coredump-launcher.socket
This package is installing a systemd unit for all users with lines --
ConditionUser=!@system
which results in endless logs of --
drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a
systemd-coredump crash was skipped because of an unmet condition check
(ConditionUser=!@system).
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.

First this must not be enabled for all users. Some users are not using
GUI or QT applications at all. In my case, this dependency was pulled
by plasma-workspace.

This can't even be disabled because --
# systemctl --user disable drkonqi-coredump-launcher.socket
The following unit files have been enabled in global scope. This means
they will still be started automatically after a successful disablement
in user scope:
drkonqi-coredump-launcher.socket

This has to be masked for the root user.

Dear Maintainer,

I think I am seeing same issue.


I have multiple DMs installed, including Plasma. But I use Gnome Shell or MATE usually,
with zero QT applications running. And Gdm as DM. This happens even on a clean reboot.


Yes, I see systemd journal spammed:


Apr 26 23:57:16 debian systemd[21468]: drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Apr 26 23:57:16 debian systemd[21468]: drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Apr 26 23:57:16 debian systemd[21468]: drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Apr 26 23:57:16 debian systemd[21468]: drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Apr 26 23:57:16 debian systemd[21468]: drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Apr 26 23:57:16 debian systemd[21468]: drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Apr 26 23:57:16 debian systemd[21468]: drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Apr 26 23:57:16 debian systemd[21468]: drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Apr 26 23:57:16 debian systemd[21468]: drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Apr 26 23:57:16 debian systemd[21468]: drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Apr 26 23:57:16 debian systemd[21468]: drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Apr 26 23:57:16 debian systemd[21468]: drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Apr 26 23:57:16 debian systemd[21468]: drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Apr 26 23:57:16 debian systemd[21468]: drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Apr 26 23:57:16 debian systemd[21468]: drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Apr 26 23:57:16 debian systemd[21468]: drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Apr 26 23:57:16 debian systemd[21468]: 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.


every 10 seconds

I cannot even uninstall it easily, because it also causes uninstall of few
other meta-packages (causing apt to show about 100 other packages to be marked
as auto installed, including plasma and some other KDE programs), and also for
example sddm themes. Which I would prefer it did not uninstall.


Cheers

Hi

Have a fresh installation on a xElite Arm64 from scratch and have the
condition error flooding my
journal too.

The fix for me,
a) add my user to group (sys)
b) edit

/usr/lib/systemd/user/drkonqi-coredump-launcher.socket

change the entry for ConditionUser to:
ConditionUser=!@sys

This fixes the issue for me.