Ksystemlog stays bright even though dark mode is set. Is this a system error

Support KDE Plasma
1

Since Manjaro Update to 25.09 Ksystemlog stays bright even though dark mode is set. Is this a system error?

2025-10-08_17-50
2025-10-08_17-50552×377 59.6 KB

2

No error. :cat_with_wry_smile:

It depends whether you enter Root’s password or continue with your own privileges, as to whether it will follow your User’s theme, or Root’s.

I just confirmed this on my system. :wink:

4 Likes
3

Thanks for your explanation! :smiley:

The strange thing is that it was dark in the previous version 25.08. Are you starting the program from the console? Because I click on it graphically as a user. And something else. It only occurs in Manjaro. For example, with a different OS, Ksystemlog is also dark as normal.

1 Like
4

When I start it from the menu, it asks for the root password and if given it uses root’s light theme - however if you click ignore then it starts as your user and of course your user’s theme is used.

You should be able to set a theme for root. I used to do it, but I haven’t in a long long time.

There are 2 obvious explanations:

  1. You’ve been clicking ignore
  2. The root user has been configured to use a dark theme

It could be both as root’s theme isn’t changed on Manjaro (unless done by the user/sys-admin), but it’s possible another distro has decided to match root’s theme to the user’s theme. I’m not aware of anyone doing that but I don’t really pay much attention to other distros.

:man_shrugging:

2 Likes
5

Thanks for your detailed explantation!

1 Like
6

Alternatively to setting root to a dark theme, you can make sure you’re a member of ‘wheel’ (giving you permission to view the logs, and disable “Run as a different user” for KsystemLog in the KDEMenuEditor or in the .desktop file.

2 Likes
7

I actually think it’s better that a different theme is used for the User and for Root; makes it easy to see that the (GUI) program is running with root privileges.

2 Likes
8

Well the first user is always added to wheel, so they probably are already.

As I suggested they’ve probably been clicking on ignore and not noticed because they already had permission.

I doubt it matters, but I think that’s there in case you need to use it from another account that doesn’t have permission, that might explain why there’s an ignore button and why it asks for the root password and not the (sudo) user’s.

Just clicking ignore is also an option.

2 Likes