I mean, it's better than back when the screen locker program crashed, your computer was just unlocked
this post was submitted on 22 Jan 2025
49 points (96.2% liked)
KDE
5643 readers
104 users here now
KDE is an international technology team creating user-friendly free and open source software for desktop and portable computing. KDE’s software runs on GNU/Linux, BSD and other operating systems, including Windows.
Plasma 6 Bugs
If you encounter a bug, proceed to https://bugs.kde.org/, check whether it has been reported.
If it hasn't, report it yourself.
PLEASE THINK CAREFULLY BEFORE POSTING HERE.
Developers do not look for reports on social media, so they will not see it and all it does is clutter up the feed.
founded 2 years ago
MODERATORS
I hate this one. It's so fucking random and I have never had a good answer as what causes it. I've found that a reboot fixes it. It usually happened after a big upgrade where you need to reboot. That's the only solution I've had for it.
I have never seen this error and don't know the cause
However, based on when it happens to you, it could be some weird caches or config files got overwritten and something did not like it. I know I've often had to delete plasma cache because something screwed up.
I’m hoping it’s fixed in later versions of Plasma. I’m on the LTS Debian release so bugs like these are to be expected :/ This aside Plasma is my favorite DE but I may switch to MATE due to nonsense like this.
It is. Using KDE on Debian is a sub par experience. I would recommend a fedora based distro if you really want the most from KDE.
Or opensuse tumbleweed!
This is hilarious!
If those steps (with no thinking or decision involved) fix the issue, then why the hell won't the system execute those commands automatically?
IIRC chvt is a privileged command, which makes sense (if an unprivileged user could execute this command they could effectively brick the computer for a local user).
That said, my understanding is that modern DE's are given a lot of access, so presumably chvt is allowed (and in this case, is required because as others mentioned, password is required). So the only other option is to fail unlocked, which is all kinds of Bad.
They require you to enter the user's password, so it still functions as a lock
I've had this happen to me a few times after waking up from sleep, I believe. Those steps did fix the issue for me.
Oh crap