(06cb:00bd) Synaptics - fprintd spams output and becomes unresponsive when not being able to recognize a print
I'm currently using the latest version of libfprint (on the master branch) with the wip/benzea/v2 branch of fprintd.
To use it, I added auth sufficient pam_fprintd.so
to the top of /etc/pam.d/sudo
, so I can simply run sudo anything
.
When I present the wrong print for more than approximately one second, the output is spammed with Place your finger on the reader again
. Sometimes, if I put the right fingerprint after this it works, sometimes it becomes unresponsive. See the following example:
Place your right index finger on the fingerprint reader
Failed to match fingerprint
Place your right index finger on the fingerprint reader
Place your finger on the reader again
Place your finger on the reader again
[about two hundred lines skipped]
Place your finger on the reader again
Place your finger on the reader again
Verification timed out
In this case, fprintd became unresponsive until it timed out.
It seems to become consistently unresponsive if you present the wrong finger (or if it just doesn't recognize it) for several seconds. Doing so also seems to make the next instance of fprintd bug. If I open a new terminal after it timed out and try again immediately it stays unresponsive even before I present any print. If I wait a bit more before trying again it gets back to the behavior I was describing above.