https://bugs.kde.org/show_bug.cgi?id=502960
--- Comment #5 from Mark Ferguson <markfe...@gmail.com> --- Something interesting I just noticed. I moved to Kubuntu 25.04 on 2 machines. Laptop via the upgrade path from 24.10 and Desktop clean install from iso (The upgrade had an unrecoverable package error so needed to do a clean install) On the laptop this issue did not appear. It was only on the Desktop with the clean install that had this issue. >From what I understand on the 24.10 to 25.04 upgrade path the systemd global user drkonqi links did not get recreated , so the existing ones where left in place. Specifically for drkonqi-coredump-launcher.socket unit there is this difference: Laptop (upgrade): > /etc/systemd/user/sockets.target.wants/drkonqi-coredump-launcher.socket Desktop (clean install): > /etc/systemd/user/sockets.target.wants/drkonqi-coredump-launcher.socket > /etc/systemd/user/sockets.target.upholds/drkonqi-coredump-launcher.socket The drkonqi-coredump-launcher.socket unit includes an UpheldBy property > UpheldBy=sockets.target UpheldBy is the reverse relationship to Upholds and this will cause the unit to constantly restart on failure. And the ConditionUser=!@system also on the unit causes a failure when run as the root user. I did a quick test on the laptop by enabling the drkonqi-coredump-launcher.socket in my user space and the extra upholds drkonqi-coredump-launcher.socket link was created. > ~/.config/systemd/user/sockets.target.upholds/drkonqi-coredump-launcher.socket Which seems to confirm the systemd global user drkonqi links did not get recreated on the upgrade path. Changing to the root user on the laptop still produces the unmet condition in the log however this only happens once. Seems there is an edge case in systemd where defining UpheldBy and a run Condition go contrary to each other. Is there another target that can be used that would not apply to the root user for the drkonqi-coredump-launcher.socket unit? -- You are receiving this mail because: You are watching all bug changes.
