Steps to reproduce: (1) Login to plasma as normal user (no root) (2) in kde menu / applications / system: select entry for ksystemlog (3) ksystemlog requests root password. The root password (although valid) is not accepted by kdesu in this context. (4) kde su again requests password stating that access was denied. I have seen this problem in relation with ksystemlog only. With other applications requiring root access, e.g. synaptic, root password works. Reproducible: Always
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.
(In reply to Justin Zobel from comment #1) > Thank you for the bug report. > > As this report hasn't seen any changes in 5 years or more, we ask if you can > please confirm that the issue still persists. > > If this bug is no longer persisting or relevant please change the status to > resolved. I'm having this exact issue with 21.12.0, Manjaro. My guess is that they have a install where you don't have a root login set, but their user can `sudo` themselves privileges which is common for a good handful of distros. So the user cannot `su` directly in this case and this is what KSystemLog is trying to do. I do acknowledge that #354106 talking about PolicyKit or anything better than giving an application effective root might be the best course of action.
Pardon, bug 354106. I'm used to GitHub's markdown.
*** Bug 451440 has been marked as a duplicate of this bug. ***
I have to confirm that this issue still exists (system deails see below). It is possible to run ksystemlog via Konsole. In Konsole enter root-mode using su + PW, then run ksystemlog: root@pucki:/home/lw# ksystemlog QStandardPaths: runtime directory '/run/user/1000' is not owned by UID 0, but a directory permissions 0700 owned by UID 1000 GID 1005 Could not find color scheme "GradientLightColorScheme" falling back to BreezeLight QStandardPaths: runtime directory '/run/user/1000' is not owned by UID 0, but a directory permissions 0700 owned by UID 1000 GID 1005 log_ksystemlog: Log manager is not yet initialized This could actually hint to an issue of missing access permission rights. Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 Kernel Version: 6.7.9-1-siduction-amd64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i5-8350U CPU @ 1.70GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: Dell Inc. Product Name: Latitude 7490
Can confirm the same issue on KDE Neon 6.3 (Ubuntu 24.04). Running from console using the standard user by typing 'ksystemlog' launches without asking for a password. This can be replicated by right-clicking KDE application menu -> Edit Applications -> selecting entry fro kjournaldbrowser, going to the 'advanced' tab, and unchecking 'run as different user' and saving. It now runs from the launcher without asking for a password. Note that next to 'run as different user' no username is entered in the 'Username' box - I don't know if this is an error or if a blank box is an accepted shorthand for 'root.' App seems to run fine at a cursory glance - but perhaps it is intended to run as root to give some extra functionality?
Hi, This bug has been seen many time on kubuntu and KDE Neon from 2020 at least on my side as well. It would be nice to solve it. It has a conundrum, assess to some types of logs require admin power. It should have some hybrid access that this prompt tries to achieve, but was not maintained. Running `$ sudo -EH ksystemlog` does the job. Why not using it?