Fprintd locks up if first fingerprint read fails

If I fail my first of three tries to read a fingerprint then I have to wait for timeout and manually enter my password.

Read/read-again calls seem to be in conflict as seen here:

Place your finger on the fingerprint reader
Failed to match fingerprint
Place your finger on the fingerprint reader
Place your finger on the reader again
Verification timed out
Password:

This also seems to be causing issues with logging in to SDDM/KDE using a fingerprint, where the prompt is not displayed at all and actually reading a fingerprint is a total gamble (dual monitor setup might be affecting stuff here). Even trying to manually enter a password here doesn't allways work.

This is on Gentoo, kernel 5.9.14, Thinkpad t495s, Prometheus Synaptics (USB:0x06CB) fingerprint reader (at latest firmware from fwupd), latest git version of libfprint, and v1.90.8 for fprintd.

My kde and sudo /etc/pam.d files are as follows (those are the only ones I've edited):

#%PAM-1.0

auth       sufficient   pam_unix.so try_first_pass likeauth nullok
auth       sufficient   pam_fprintd.so

auth       required     pam_nologin.so
auth       include      system-local-login

account    include      system-local-login

password   include      system-local-login

session    include      system-local-login`

# File autogenerated by pamd_mimic in pam eclass

auth    sufficient              pam_fprintd.so
auth    substack                system-auth
account substack                system-auth
session substack                system-auth

Just checked by logs, looks like I'm also getting the following on occasion:

pam_unix(sudo:auth): conversation failed
pam_unix(sudo:auth): auth could not identify password for [MY_USERNAME]