https://bugs.kde.org/show_bug.cgi?id=499893
--- Comment #7 from chws...@outlook.com --- (In reply to chwshka from comment #4) > I think that I've also made another breakthrough. I noticed that if I wake > the machine from sleep very quickly, the fingerprint authentication option > is still there. Under System Settings > Screen Locking I have the "Delay > before password required" option set to 30 seconds. If I wake the laptop > from sleep before 30 seconds, the fingerprint option is there, but if I wake > the laptop after longer than 30 seconds the fingerprint option is no longer > there. > > I can replicate this behaviour with other time delays for the "Delay before > password required" setting. However setting this to "Never require a > password" simply means that the machine never locks and isn't suitable for > anyone with any security considerations. > > So could this be an issue with my settings under pam.d? I'm a bit lost with > these settings and especially lost when it comes to how they interact with > kscreenlocker Following on from this. I've set the "Delay before password required" setting to "Never require a password". When I wake the computer from sleep I noticed that the "or scan your fingerprint on the reader" message is still there on the lock screen and is functional. If I put my finger to the reader, it unlocks. If I use an incorrect finger, it gives the usual error. Although because the "Never require a password" setting is in effect, I can also just hit any key or move the mouse to unlock. So beyond the fprintd polkit errors that I previously mentioned, this regression seems related to the "Delay before password required" option. -- You are receiving this mail because: You are watching all bug changes.
