KDE screen lock not accepting correct password on Ubuntu 24.04

DanielSilva

New Member
Joined
Aug 25, 2024
Messages
23
Reaction score
5
Credits
231
Good afternoon, I am using Ubuntu 24.04 and when I lock the screen with Ctrl + L, it simply says that my password is incorrect even though it isn’t. I have already updated KDE to the latest version, and it still doesn’t work at all.
 


Good afternoon, I am using Ubuntu 24.04 and when I lock the screen with Ctrl + L, it simply says that my password is incorrect even though it isn’t. I have already updated KDE to the latest version, and it still doesn’t work at all.
If your password is indeed correct, but it is not accepted, there are a number of things you can do, but at first, it's worth double checking the password. Sometimes an inadvertent Caps Lock on the keyboard may be set which could render an incorrect password. That's tripped me up in the past.

Test the password on some other app to see that it is indeed correct. For example, in a terminal you could use the password in a sudo command which will, by default, ask for your password if that hasn't been configured otherwise. For example:
Code:
sudo blkid

Test the password in a virtual console by switching to one pressing the keys: ctrl+alt+F3, or whichever F function key is available, and logging in with the password to see if it works.

If the password is indeed correct, then one can just kill the kde screen locker. Not having used kde for some time now, I can't give an exact command, but you can find out the process number (PID) with a ps command, something like:
Code:
ps aux | grep kdescreenlock

ps aux | grep kde
Once the pid is identified, you can kill it in a virtual console, or a terminal with something like:
Code:
kill <PID>
where <PID> is the process ID number, without the pointy brackets. Then check the ps command to see that it no longer runs. If it persists, one can try: kill -9 <PID>.

If there's a bug in the screenlocker, it can be disabled in the configurations. If the same issue recurs on a full cold reboot, then there may be a bug to simply avoid by using another screenlock or not using one.
 
Guys, sorry for not informing what I did.


So, the locker screen uses the unix_chkpwd file,
but I noticed it didn’t have the SUID bit set, as shown below:

root@hostdime:/etc/strongswan.d/charon# ls -lhi /sbin/unix_chkpwd
1453460 -rwxr-sr-x 1 root shadow 31K Jun 12 10:45 /sbin/unix_chkpwd
root@hostdime:/etc/strongswan.d/charon#

What I did was remove the GUID bit and add the SUID bit using the command:

chmod u+s /sbin/unix_chkpwd
 


Follow Linux.org

Members online


Top