I encountered a funny bug in KDEs system settings. This bug is only present in Manjaro. I have another machine running Fedora, where this bug can not be reproduced.
I ran Manjaro KDE with German Locale, set my energy options (among others) on first startup and noticed that after a short while some of those settings were overridden.
I opened system settings and clicked on energy management (all in German).
And as soon as I clicked, system settings would freeze and never recover.
Note, that this was not the case after first startup. But it was 100% reproducible from here on.
When I changed the language to English, the reboot from within system settings would not work. I had to force shut down. (Another minor bug that I did not investigate.)
However, once the machine booted, my system was set to English and I could access energy management options.
Very strange.
I set the system to German again, reboot again failed from within settings. After next startup the system was back to German and energy management again froze system settings never to recover.
Since I myself donāt mind my system being set to English, this is rather anecdotal.
Still I wanted to share this strange bug with you.
I skimmed the bugtracker and havenāt found anything yet.
The search function and tag system is a little much at a first glance. (Also, thank you, @Aragorn for tagging this post. I thought I had done that.)
Hey, @Kobold!
Itās very nice of you to try to help.
However, the How To is not applicable. This is just a test system.
With German lang setting only the system settings GUI broke whenever I tried to access energy options through GUI. (But only after a whileā¦ Which kind of hampers my overall trust.)
But everything else stayed responsive.
After GUI reboot (after lang change) the screen is black, only the cursor remains.
I didnāt bother starting a tty and honestly, I donāt care that much.
There was no chance of data loss. This whole machine is for testing. First pure AMD machine, first time Manjaro.
And of course switching two or more things at the same time is just bad and lazy testing.
I had my shot. Will go back to known good on other machine with the AMD machine. And then go on from there.
It is good that you show this problem to otherās, it helps that other german KDE userās can evade it but here are no KDE Developerās around.
The only stuff that happenās around here when you report KDE errorās, is mainly to get attention and otherās who maybe show you a workaround.
The real fix is mostly created by a maintainer or a developer.
Im german too btw.
But i prefer to let my OS run in english, because it makes more sense to use it in english when all tutorials are in english and the most userās are native english speakerā¦ also the errorās and logs will shown in (D)english which complicated the situation if someone looking for help.
Spoiler alert: We germanās say Denglish to something that is bad translated. Because German/(D)eutsch the reason to call something Denglish.
Not sure if other non native english speakerās use this jokeās too.