DrKonqi spams journal with "unmet condition check"

I’m running openSUSE Tumbleweed (currently 20250414) mit KDE und Graphics Platform Wayland. Since ~2 weeks my log get bloated by complaints from DrKonqi, claiming every couple of seconds that:

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

and that

systemd[1234]: 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.

Any idea how to fix this?

Hi! I’m not sure if this was your ticket, but just to put the link here as a reference for folks - this has been reported in the KDE Bugtracking System: 502960 – DrKonqi: Socket launch skipped because of an unmet condition check (ConditionUser=!@system).

In the meantime I dropped a report at https://bugs.kde.org/show_bug.cgi?id=502960, where by now you can find a preliminary fix - as also mentioned by @johnandmegh.