https://bugs.kde.org/show_bug.cgi?id=502960
--- Comment #31 from R. Horvat <[email protected]> --- (In reply to Alex Atkinson from comment #29) > (In reply to Mike from comment #28) > > I suggest making a new group for this, putting root in it... then packages, > > I.E. pipewire, can put their user in it... or some other way packages can > > grow this mask. > > The question I have on the > [PR](https://invent.kde.org/plasma/drkonqi/-/merge_requests/373) is which > KDE components, if any, run as root... I would be surprised if any. My > sysadmin brain says it should be explicitly denied (as intended with the PR > that introduced _this bug_), but here we have this scenario where drkonqi > was running as root -- as seen with at least OpenSUSE and Kubuntu. > > While my above posted "fix" solves for this bug while preserving the drkonqi > for root, I would more strongly suggest simply disabling drkonqi for root. > This would align the distros with KDE's design choice. Hm, my solution to simply increase logging threshold by adding: <code> [Socket] LogLevelMax=err </code> To the systemd file should preserve original intent (to disable drkonqi for root) and satisfy admins by not overwhelming log with meaningless messages. The override can simply be added by adding above lines with: #sudo systemctl edit --user drkonqi-coredump-launcher.socket -- You are receiving this mail because: You are watching all bug changes.
