1. Configure fprintd in /etc/pam.d/kde-fingerprint: > auth [success=1 default=ignore] pam_fprintd.so max_tries=1 timeout=10 > auth substack system-auth-local > auth required pam_permit.so > account include system-auth-local > password include system-auth-local > session include system-auth-local 2. Lock screen 3. Wait until fprintd finishes with timeout (in my case it asks for password) kscreenlocker UI hides at this moment 4. Show UI back 5. Try to unlock with fingerprint Observed: does not unlock Expected: unlocks successfully
Probably duplicate of https://bugs.kde.org/show_bug.cgi?id=499893
(In reply to Oleg Solovyov from comment #0) > 2. Lock screen > 3. Wait until fprintd finishes with timeout (in my case it asks for password) > kscreenlocker UI hides at this moment > > 4. Show UI back > 5. Try to unlock with fingerprint At this point, do you see a prompt near the password input to log in with your fingerprint? If you do *not* see that, this is probably a duplicate of bug 499893 Otherwise, it's different. In this case, would you get system logs with journalctl, starting about a minute before you see the fingerprint login fail? Adjust the date and time accordingly, and use this command: journalctl --since "2020-07-10 15:10:00" Then save the output to a file and attach it to this report. Thanks!