492315 2024-08-28 12:30:08 +0000 Fails to unlock with fprint is pam_fprintd configured with timeout 2026-03-02 16:01:33 +0000 1 1 4 Plasma plasmashell Screen locking 6.2.4 Other Linux RESOLVED WORKSFORME https://bugs.kde.org/show_bug.cgi?id=499893 NOR normal 1.0 0 mcpain plasma-bugs-null jami.pcwpsx3u kdedev nate sycxyc+kde zerg 0 oldest_to_newest 2349398 0 mcpain 2024-08-28 12:30:08 +0000 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 2408717 1 jami.pcwpsx3u 2025-03-18 09:04:03 +0000 Probably duplicate of https://bugs.kde.org/show_bug.cgi?id=499893 2409397 2 kdedev 2025-03-20 14:47:13 +0000 (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! 2412996 3 bug-janitor 2025-04-04 03:46:38 +0000 🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone! 2417076 4 bug-janitor 2025-04-19 03:47:21 +0000 🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.