https://bugs.kde.org/show_bug.cgi?id=502960
--- Comment #21 from R. Horvat <[email protected]> --- (In reply to R. Horvat from comment #20) > (In reply to Hector from comment #19) > > Is it ok to just remove the condition? will that be dangerous or break > > something? > > I did remove the condition in the end on my personal system, and it's now > working normally. > I'm not sure if there are any security ramifications for servers (since this > condition should prevent daemon to start as root user, but only when you log > in as root, or do a su command to become root). I found another (better) solution (it doesn't involve removing the condition, it just limits the amount of information that gets to the log): In '/usr/lib/systemd/user/drkonqi-coredump-launcher.socket' file I added new line: [Socket] LogLevelMax=err The line limits the amount of log information that gets to the systemd logs for this particular socket (only errors and higher level messages get to the log), as per specification: https://manpages.debian.org/trixie/systemd/systemd.exec.5.en.html The beautiful thing about this is that some other systemd services that emit similar warning, notice or info messages can be silenced in a similar fashion. -- You are receiving this mail because: You are watching all bug changes.
