SUMMARY See video. Often, the fingerprint wouldn't be registered until I enter the wrong password once, only then it accepts the fingerprint STEPS TO REPRODUCE 1. set up fingerprint 2. lock screen 3. try to unlock using fingerprint reader OBSERVED RESULT Screen doesn't unlock EXPECTED RESULT Screen should unlock SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240206 KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.1 Kernel Version: 6.7.2-1-default (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 7840U w/ Radeon 780M Graphics Memory: 30.5 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: Framework Product Name: Laptop 13 (AMD Ryzen 7040Series) System Version: A7 ADDITIONAL INFORMATION I made a video: https://www.youtube.com/watch?v=KmxRadbhnzI
I can confirm this bug on a Lenovo ThinkPad T14 Gen1 and also on a Lenovo ThinkPad X1 Yoga Gen 3. Both running openSUSE Tumbleweed with Plasma 6.2.0
Can either of you test with Plasma 6.3.2? Improvements have been made to fingerprint scanning and unlocking On 6.3.2, if I lock my screen and move the mouse, I see the prompt to unlock with the fingerprint reader, and it works on the first try.
(In reply to TraceyC from comment #2) > Can either of you test with Plasma 6.3.2? Improvements have been made to > fingerprint scanning and unlocking > On 6.3.2, if I lock my screen and move the mouse, I see the prompt to unlock > with the fingerprint reader, and it works on the first try. (In reply to TraceyC from comment #2) > Can either of you test with Plasma 6.3.2? Improvements have been made to > fingerprint scanning and unlocking > On 6.3.2, if I lock my screen and move the mouse, I see the prompt to unlock > with the fingerprint reader, and it works on the first try. For me, it actually got worse. On the lockscreen, the fingerprint unlock is only possible on about 25% of attempts on Plasma 6.3.2 I tried to follow the opensuse documentation for fingerprint unlocking: https://en.opensuse.org/SDB:Using_fingerprint_authentication I ran sudo pam-config --update --fprintd which didn't fix anything and my configs in /etc/pam.d/kde looks like this: #%PAM-1.0 # This service is only used by kcheckpass for unlocking, # so only auth is really relevant here. auth include common-auth account include common-account password include common-password auth sufficient pam_unix.so try_first_pass likeauth nullok auth sufficient pam_fprintd.so I also tried this #%PAM-1.0 # This service is only used by kcheckpass for unlocking, # so only auth is really relevant here. auth sufficient pam_unix.so try_first_pass likeauth nullok auth sufficient pam_fprintd.so auth include common-auth account include common-account password include common-password But that didn't change anything. /var/lib/pam.d/kde-fingerprint looks like this #%PAM-1.0 # for fingerprint auth required pam_fprintd.so auth include common-auth account include common-account password include common-password fingerprint authentication works perfectly every time for sudo and polkit, but not the lockscreen. I guess it is also worth mentioning that I'm on openSUSE Kalpa now, which is immutable, but uses the same packages as Tumbleweed. This means that /var/lib/pam.d/kde looks different to the /etc version, but the /etc version should have precendence, right? I'm also wondering why it works sometimes and sometimes not. I also already had the case (multiple times actually) that I couldn't unlock my screen AT ALL, it didn't accept my password nor my fingerprint - so I had to reboot my machine, which is very annoying. Should I open a new bug for the latter issue? Do you need any other configs? :)
Thanks for the additional details. That lets us know it's not pam or fprintd, but probably in the lock screen code. I'll let a contributor more experienced with that area take it from here.