https://bugs.kde.org/show_bug.cgi?id=502960

Craig Andersen <ace6...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ace6...@gmail.com

--- Comment #4 from Craig Andersen <ace6...@gmail.com> ---
I had the multiple  message (16) every about 10 seconds. 
Decide to remove the package to silence the message. On tumbleweed 20250417
(latest) using KDE X11.

[1] erase drkonqi6-6.3.4-1.1.x86_64: success

[2] rebooted, no messages.

Installed it back.
[3] install drkonqi6-6.3.4-1.1.x86_64: success
[4] rebooted

It looks like it is proper now, no extra messages.

User 1000 Active
systemctl --user status drkonqi-coredump-launcher.socket

● drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a
systemd-coredump crash
     Loaded: loaded (/usr/lib/systemd/user/drkonqi-coredump-launcher.socket;
disabled; preset: enabled)
     Active: active (listening) since Sat 2025-04-19 09:36:25 CDT; 3h 27min ago
 Invocation: e42036a0ab414a759d7b1d7bf6315eb6
     Listen: /run/user/1000/drkonqi-coredump-launcher (SequentialPacket)
   Accepted: 0; Connected: 0;
     CGroup:
/user.slice/user-1000.slice/user@1000.service/app.slice/drkonqi-coredump-launcher.socket

ROOT USER (inactive dead)
○ drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a
systemd-coredump crash
     Loaded: loaded (/usr/lib/systemd/user/drkonqi-coredump-launcher.socket;
disabled; preset: enabled)
     Active: inactive (dead)
  Condition: start condition unmet at Sat 2025-04-19 09:37:11 CDT; 3h 47min ago
             └─ ConditionUser=!@system was not met
     Listen: /run/user/0/drkonqi-coredump-launcher (SequentialPacket)
   Accepted: 0; Connected: 0;

Apr 19 09:37:11 plato systemd[17365]: Socket to launch DrKonqi for a
systemd-coredump crash was skipped because of an unmet condition check
(ConditionUser=!@system).

Only that one initialization message in log (09:37).

It seems like an update on about April 8 started this and did not update
correctly ?!

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to