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

            Bug ID: 502960
           Summary: DrKonqi: Socket launch skipped because of an unmet
                    condition check (ConditionUser=!@system).
    Classification: Applications
           Product: drkonqi
           Version: unspecified
          Platform: openSUSE
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: backtraceparsing
          Assignee: plasma-b...@kde.org
          Reporter: zeitli...@yahoo.de
  Target Milestone: ---

SUMMARY
drkonqi6-6.3.4-1.1.x86_64 on openSUSE Tumbleweed fills the journal repetitively
every few seconds with failure msgs of type:
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.

STEPS TO REPRODUCE
1. upgrade to drkonqi6-6.3.4-1.1.x86_64 on openSUSE Tumbleweed
2. boot
3. inspect journal

OBSERVED RESULT
I get repetitive blocks of failure messages from drkonqi in my journal every
few seconds.
This has started on my machine with drkonqi6-6.3.4-1.1.x86_64  and exactly
after booting the system at 19:33:04 on Apr 11 after system upgrade.

Apr 11 19:33:13 machn systemd[2618]: Socket to launch DrKonqi for a
systemd-coredump crash was skipped because of an unmet condition check
(ConditionUser=!@system).
Apr 11 19:33:13 machn systemd[2618]: Socket to launch DrKonqi for a
systemd-coredump crash was skipped because of an unmet condition check
(ConditionUser=!@system).
Apr 11 19:33:13 machn systemd[2618]: Socket to launch DrKonqi for a
systemd-coredump crash was skipped because of an unmet condition check
(ConditionUser=!@system).
Apr 11 19:33:13 machn systemd[2618]: Socket to launch DrKonqi for a
systemd-coredump crash was skipped because of an unmet condition check
(ConditionUser=!@system).
Apr 11 19:33:13 machn systemd[2618]: Socket to launch DrKonqi for a
systemd-coredump crash was skipped because of an unmet condition check
(ConditionUser=!@system).
Apr 11 19:33:13 machn systemd[2618]: Socket to launch DrKonqi for a
systemd-coredump crash was skipped because of an unmet condition check
(ConditionUser=!@system).
Apr 11 19:33:13 machn systemd[2618]: Socket to launch DrKonqi for a
systemd-coredump crash was skipped because of an unmet condition check
(ConditionUser=!@system).
Apr 11 19:33:13 machn systemd[2618]: Socket to launch DrKonqi for a
systemd-coredump crash was skipped because of an unmet condition check
(ConditionUser=!@system).
Apr 11 19:33:13 machn systemd[2618]: Socket to launch DrKonqi for a
systemd-coredump crash was skipped because of an unmet condition check
(ConditionUser=!@system).
Apr 11 19:33:13 machn systemd[2618]: Socket to launch DrKonqi for a
systemd-coredump crash was skipped because of an unmet condition check
(ConditionUser=!@system).
Apr 11 19:33:13 machn systemd[2618]: Socket to launch DrKonqi for a
systemd-coredump crash was skipped because of an unmet condition check
(ConditionUser=!@system).
Apr 11 19:33:13 machn systemd[2618]: Socket to launch DrKonqi for a
systemd-coredump crash was skipped because of an unmet condition check
(ConditionUser=!@system).
Apr 11 19:33:13 machn systemd[2618]: Socket to launch DrKonqi for a
systemd-coredump crash was skipped because of an unmet condition check
(ConditionUser=!@system).
Apr 11 19:33:13 machn systemd[2618]: Socket to launch DrKonqi for a
systemd-coredump crash was skipped because of an unmet condition check
(ConditionUser=!@system).
Apr 11 19:33:13 machn systemd[2618]: Socket to launch DrKonqi for a
systemd-coredump crash was skipped because of an unmet condition check
(ConditionUser=!@system).
Apr 11 19:33:13 machn systemd[2618]: Socket to launch DrKonqi for a
systemd-coredump crash was skipped because of an unmet condition check
(ConditionUser=!@system).
Apr 11 19:33:13 machn systemd[2618]: 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.

EXPECTED RESULT
An occasional log to the journal from drkonqi of type

Apr 10 11:22:33 machn systemd[1947]: Listening on Socket to launch DrKonqi for
a systemd-coredump crash.
Apr 10 11:22:36 machn systemd[1947]: Started Consume pending crashes using
DrKonqi.
Apr 10 11:22:43 machn systemd[1881]: Closed Socket to launch DrKonqi for a
systemd-coredump crash.
Apr 10 11:23:37 machn systemd[1947]: Started Launch DrKonqi for a
systemd-coredump crash (PID 2296/UID 1000).

This has been the case up to drkonqi6-6.3.3-1.1.x86_64, which was before Apr.
11 on my machine.

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20250414
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.12.0
Qt Version: 6.9.0
Kernel Version: 6.14.1-1-default (64-bit)
Graphics Platform: Wayland

ADDITIONAL INFORMATION

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

Reply via email to