https://bugs.kde.org/show_bug.cgi?id=502960
--- Comment #8 from Mark Ferguson <[email protected]> --- Looking closer at the drkonqi-coredump-launcher.socket systemd unit source points to the potential problem https://github.com/KDE/drkonqi/blame/master/src/coredump/launcher/drkonqi-coredump-launcher.socket 2 months ago the condition check got added to the file > ConditionUser=!@system This is the last section in the file > # Prevents trigger-limit-hit failure state by restarting the unit (systemd > 250[?]) > UpheldBy=sockets.target Having the unit defined in the systemd global user space means it can be enabled automatically for any logged in user. The condition check on the system users seems an improvement however in combination with the UpheldBy option this causes a continuous failure when the unit is enable for the root user (sudo to root is enough to trigger this action) I am not that familiar with systemd to know if there is another way to configure the unit so it would not run as the root user but also allow the restart functionality for other users. Hopefully this is a common scenario otherwise it probably should be raised as a feature request to the systemd project. -- You are receiving this mail because: You are watching all bug changes.
