https://bugs.kde.org/show_bug.cgi?id=499893
--- Comment #4 from chws...@outlook.com --- Created attachment 178274 --> https://bugs.kde.org/attachment.cgi?id=178274&action=edit fprintd journal logs after polkit changes I've done some digging and it seems like the fprintd errors are polkit related. Based on this comment (https://github.com/i3/i3lock/issues/210#issuecomment-1033042602) I created two rules in this directory '/etc/polkit-1/rules.d/': 50-net.reactivated.fprint.device.claim.rules and 50-net.reactivated.fprint.device.verify.rules After creating these rules, I'm no longer getting the fprintd authorisation denied messages in my journal logs. However the fingerprint authentication is still failing to appear on the unlock screen after the machine goes to sleep. 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 -- You are receiving this mail because: You are watching all bug changes.
