SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Upon opening ksystemlog im presented with a prompt for the root password, after entering the password access is denied saying that I may need to be a user in the group wheel. There is no group "wheel". 2. 3. OBSERVED RESULT unable to access system logs EXPECTED RESULT accessing system logs upon entering the root password SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.53.5 KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
I'm observing the same behavior with kubuntu 22.04 (plasma 5.24.3, kde framework 5.92.0), and it seems to be related to starting ksystemlog via kdesu (when using the provided .desktop file), in this case the password request is handled by: /usr/bin/sudo -u root /usr/lib/x86_64-linux-gnu/libexec/kf5/kdesu_stub - The password will always be rejected and the second and thirds try a slightly different password dialogue is shown. As ksystemlog has not started during password prompt, I would assume that the bug is not directly related to ksystemlog (btw, ksystemlog seems to be the only app in kubuntu which is started in this way, i.e. by stating "X-KDE-SubstituteUID=true" in its desktop file).
Have the same problem in Arch Linux (plasma 5.25, plasma-framework 5.95.0), along with the 1st, 2nd, and 3rd tries all using different password dialogs just as Daniel Frein is having. Removing the line: X-KDE-SubstituteUID=true Allows me to start KSystemLog properly without entering a password as I'm a member of the 'wheel' group. I think it should be preferred to require the user to be a member of the 'wheel' group (by not substituting UID), rather than requiring logging in with the actual 'root' user password which as of now doesn't even work.
This bug has been around for years now.
*** This bug has been marked as a duplicate of bug 358118 ***