SUMMARY With Fingerprints enrolled, putting in my password is not accepted as a valid unlocking method. It prompts for the fingerprint after entering password and enter, then says unlocking failed STEPS TO REPRODUCE 1. lock screen 2. enter password 3. promted for fingerprint, even tho password has been supplied 4.enter password again 5. unlocking failed OBSERVED RESULT Only fingerprint can unlock my session EXPECTED RESULT A password unlocked session SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora KDE 35 KDE Plasma Version: 5.23.90 KDE Frameworks Version: 5.90 Qt Version: 5.15 ADDITIONAL INFORMATION I am using Marc Deop's plasma beta build for Fedroa https://copr.fedorainfracloud.org/coprs/marcdeop/plasma/
This message is coming straight from fprint, so it's a finger recognition issue in fprint itself. Unfortunately there's nothing we can do about it in KDE code. I sometimes get the same thing and have to do it a few times before my finger is accepted. And I've notices that when my fingers are wet, it won't work. I was unable to unlock right after coming out the shower the other day lol
isnt it a kscreenlocker logic issue tho? - if a password has been supplied, it should straight out skip the fprint part and unlock normally
Ohh! Sorry, I misread the issue. Nonetheless, it is still an upstream issue, albeit a different one. When fprint auth is in use, polkit prevents using your password. You can see this in non-kscreenlocker polkit auth prompts as well. It really shouldn't do this. But I think this is an issue in polkit itself. (CCing David Edmundson who can correct me if I'm wrong)
I was looking further into this and came across the archwiki suggestion (https://wiki.archlinux.org/title/Fprint#Login_configuration) for /etc/pam.d/kde config file to add auth sufficient pam_unix.so try_first_pass likeauth nullok essentially if password null, ask for fprint, but it looks like plasma generates these files using authselect, so I was hesitant to mess with them as I dont really want to break my config