https://bugs.kde.org/show_bug.cgi?id=502960
Mark Ferguson <markfe...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |markfe...@gmail.com
--- Comment #1 from Mark Ferguson <markfe...@gmail.com> ---
I have experienced the same issue after recently upgrading to Kubuntu 25.04.
I managed to find out what I think is the problem.
It turns out the drkonqi-coredump-launcher.socket unit is in the global user
space and runs for the root user which is not allowed by the user condition
(ConditionUser=!@system). This is why the logs get flooded.
Run as root:
> systemctl --user status drkonqi-coredump-launcher.socket
The systemd global user space is located in the etc directory /etc/systemd/user
I am not sure if the drkonqi-coredump-launcher.socket unit should be in the
global user space or it is the incorrect target. Maybe a different target would
prevent it starting as the root user i.e. a graphical target instead of the
socket target.
The fix is to disable the global unit for drkonqi-coredump-launcher.socket
Run as root:
> systemctl --global disable drkonqi-coredump-launcher.socket
It maybe required to then enable the drkonqi-coredump-launcher.socket in the
local user space.
Run as user:
> systemctl --user status drkonqi-coredump-launcher.socket
If disabled run:
> systemctl --user enable drkonqi-coredump-launcher.socket
To check all drkonqi units run this command:
> systemctl --user status drkonqi*
@drkonqi maintainers is the systemd configuration something provided in the
software package or is it related to the distribution package?
--
You are receiving this mail because:
You are watching all bug changes.
