Hi,

I deleted my config to fix a couple of problems with crashes on startup and now I have a new one: The lockscreen doesn't accept my password. I am using colemak so I tried typing it in both colemak and qwerty, but neither works. It just tells me "Unlocking failed" and forces me to restart my session. Is anyone else experiencing this? It's kind of hard to do any diagnosis because there is no way to check whether your keyboard layout works and of course you can't do anything else, because the screen is locked.
I'm using KF 5.1 and Plasma 5.0

Cheers,
Malte

maybe:
login to a Plasma 5.0 session as another user (or root) then run systemsettings as your account and change the lockscreen password there

Code: Select all

 kdesu -u your_user_name systemsettings

Sorry, but how would I change my lockscreen password? I wasn't aware that there even is a seperate password for it.

I meant your change your password or you could disable the screen locker

If you switch to qwerty does the screen saver lock work correctly, I assume that colemak worked correctly earlier

Changing my password doesn't make a difference. I can log in and everything. But the screen locker doesn't accept it. Changing to qwerty still doesn't work. The problem with changing the password is, I can't even change the session once the screen is locked. So really all I can do is forcibly restart the Xserver. I disabled the screen locker for now, but that's just a workaround.

there are some similar bug reports:

this is most appropriate as it's for Kscreen5 but there's not much to the report, you should might confirm this or post a new one if you feel your issue is different:
https://bugs.kde.org/show_bug.cgi?id=337910

reports for KDE4.x
https://bugs.kde.org/show_bug.cgi?id=323339
https://bugs.kde.org/show_bug.cgi?id=177450
https://bugs.kde.org/show_bug.cgi?id=314661

I could assume it's related to https://bugs.kde.org/show_bug.cgi?id=314661 - ie. kcheckpass either has insufficient permissions or is not -or the KDE4 version might be- resolved?

Since the screenlocker uses PAM, I doubt there's a special password (written in cleartext in the config *lol* for the locker anywhere.
-> What "config" did you delete precisely (ie. which folder?) - might have impacted the binary lookup path...

Pro tip from Cpt. Hindsight:
*NEVER* delete configurations to resolve an issue - *RENAME* them.
Just as good and allows for inspection of the culprit =)