https://bugs.kde.org/show_bug.cgi?id=502960
Alex Atkinson <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #24 from Alex Atkinson <[email protected]> --- This patch affects the intent of commit [7dca985](https://github.com/KDE/drkonqi/commit/7dca985d21d76a98b4d39196404060c928afb9f4) while allowing downstream consumers of the product to continue to implement it under their 'root' system user -- an established practice. I tried to cut a [PR](https://github.com/KDE/drkonqi/pull/1/commits/e049a7c0464d51790012b424aa3af5bc2903b0ee) against their Github mirror. :/ The docs on contributing are rather broken... I'll figure it out another time, but for now this will solve the issue for folks. Either apply the change from the PR manually, or patch it. Note that setting up the patching method will allow you to re-apply it easily if needed. PATCHFILE: ```patch --- /usr/lib/systemd/user/drkonqi-coredump-launcher.socket 2025-12-16 19:13:22.316780454 -0500 +++ drkonqi-coredump-launcher.socket.x 2025-12-16 19:13:56.551805541 -0500 @@ -4,7 +4,8 @@ [Unit] Description=Socket to launch DrKonqi for a systemd-coredump crash DefaultDependencies=no -ConditionUser=!@system +ConditionUser=|!@system +ConditionUser=|root [Socket] # This is a bit problematic. Technically the user should be able to set the runtime dir via env as well, but we need ``` 1. Save the above (not including the '```' lines) to drkonqi-coredump-launcher.socket.patch. 2. Run (root/sudo): `patch /usr/lib/systemd/user/drkonqi-coredump-launcher.socket drkonqi-coredump-launcher.socket.patch` 3. Run (root/sudo): `systemctl --user daemon-reload` 4. Run (root/sudo): `systemctl --user enable --now drkonqi-coredump-launcher.socket` If folks are in an odd state from previous efforts in attempting to fix this: 0. Revert /usr/lib/systemd/user/drkonqi-coredump-launcher.socket if needed. Found [here](https://github.com/KDE/drkonqi/blob/master/src/coredump/launcher/drkonqi-coredump-launcher.socket). 1. Ensure that `systemctl status drkonqi-coredump-launcher.socket` returns ~"could not be found", or is disabled. 2. Run (root/sudo): `systemctl enable [email protected]` 3. Run (root/sudo): `systemctl --user enable --now drkonqi-coredump-launcher.socket` At this point, `systemctl --user status drkonqi-coredump-launcher.socket` should return the following for the 'root' user as well as your other non-root, non-system users. ● drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash Loaded: loaded (/usr/lib/systemd/user/drkonqi-coredump-launcher.socket; enabled; preset: enabled) Active: active (listening) since Tue 2025-12-16 18:19:16 EST; 1h 7min ago Verify by watching your syslog for a minute or two. `tail -f /var/log/syslog`. -- You are receiving this mail because: You are watching all bug changes.
