[kscreenlocker] [Bug 453877] If fingerprint authentication is enabled, unable to unlock screen with password until after 3 failed fingerprint auth attempts

https://bugs.kde.org/show_bug.cgi?id=453877 --- Comment #4 from Éric Brunet --- I agree it should be PAM's job, but they don't seem to think so. From the manpage for pam_fprintd: The PAM stack is by design a serialised authentication, so it is not possible for pam_fprintd to allow

[kscreenlocker] [Bug 453877] If fingerprint authentication is enabled, unable to unlock screen with password until after 3 failed fingerprint auth attempts

https://bugs.kde.org/show_bug.cgi?id=453877 --- Comment #3 from Nate Graham --- Yeah I'm pretty sure this is a PAM issue unfortunately. -- You are receiving this mail because: You are watching all bug changes.

[kscreenlocker] [Bug 453877] If fingerprint authentication is enabled, unable to unlock screen with password until after 3 failed fingerprint auth attempts

https://bugs.kde.org/show_bug.cgi?id=453877 Éric Brunet changed: What|Removed |Added CC||eric.bru...@lps.ens.fr --- Comment #2 from Éric

[kscreenlocker] [Bug 453877] If fingerprint authentication is enabled, unable to unlock screen with password until after 3 failed fingerprint auth attempts

https://bugs.kde.org/show_bug.cgi?id=453877 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Component|greeter