Alternate method of fingerprint detection on Lock Screens
This isn't an issue.
First, thank you for your library. It is great to have my dell fingerprint reader working.
I wanted to point you to something I wrote last night that has concepts that you'd be welcome to borrow for a more official release. I threw together this small perl script: https://github.com/rhandom/fprintd-detect
The existing solution offering to use frpintd via PAM is a bit problematic - there are plenty of cases where I didn't want to block while waiting for the fingerprint reader, and many backend cases that wouldn't make sense to use that way.
This script I put together will:
- Listen for when a ScreenSaver is activated
- Listen for when a computer is sent to Suspend or Unsuspend (have only added KDE DBus events for now)
- When the ScreenSaver is activated, claim the fprintd device and begin listening.
- Continue VerifyStart until a verify-match is received
- At verify-match use dbus to unlock the session
- If the session is unlocked for any other reason, the fprintd claim is released
- This script works both with the fprintd service, or without it via the fprintd-verify script.
This does not support using the thumbprint for the initial login (since at that point my user's .config/autostart won't have run)
This does support fingerprint during normal lock, and during resume from suspend. It works very well. There is no timeout if the user wants to enter their normal user password.
Again, thank you for fprintd work. And let me know if you have any questions about fprintd-detect (I can rename it if the name is wrong, but I would love for some scripts like this (either perl or python or even a c implementation) to be included with fprintd itself (once adding support for hibernate, and non-kde desktops)