It’s been a while since you’ve posted - not sure if you have resolved this or not.
I have no solution in this post, but the following might help you troubleshoot.
Today, I woke my device from sleep and the fingerprint reader would not work. After entering my password, I was able to use the fingerprint reader for a sudo command on the cli.
sudo journalctl -r -n 1000 | grep fprintd
Jul 08 10:17:49 fw13 systemd[1]: fprintd.service: Deactivated successfully.
Jul 08 10:17:16 fw13 systemd[1]: Started fprintd.service - Fingerprint Authentication Daemon.
Jul 08 10:17:16 fw13 systemd[1]: Starting fprintd.service - Fingerprint Authentication Daemon...
Jul 08 10:17:16 fw13 dbus-daemon[1153]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.26022' (uid=0 pid=74769 comm="/usr/bin/sudo journalctl -r -n 100" label="unconfined")
Jul 08 10:15:01 fw13 systemd[1]: fprintd.service: Deactivated successfully.
Jul 07 22:24:25 fw13 kscreenlocker_greet[62646]: pam_fprintd(kde:auth): ReleaseDevice failed: Release failed with error: The device is still busy with another operation, please try again later.
Jul 07 22:24:25 fw13 fprintd[73048]: Device reported an error during verify: Cannot run while suspended.
Jul 07 22:24:23 fw13 systemd[1]: Started fprintd.service - Fingerprint Authentication Daemon.
Jul 07 22:24:22 fw13 systemd[1]: Starting fprintd.service - Fingerprint Authentication Daemon...
Jul 07 22:24:22 fw13 dbus-daemon[1153]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.25997' (uid=1000 pid=62646 comm="/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet" label="unconfined")
So it looks like fprinted had an issue as the device was going into s2idle (sleep) i.e.
22:24:25 fw13 kscreenlocker_greet[62646]: pam_fprintd(kde:auth): ReleaseDevice failed: Release failed
Jul 07 22:24:25 fw13 fprintd[73048]: Device reported an error during verify: Cannot run while suspended.
I have no clue if this is the reason, fprinted did not work for me after waking the device from sleep (at about 10:14-10:15). I regularly sleep the device and don’t have issues. greping through journalclt back to late May, I see only one instance of the ReleaseDevice failed which happened yesterday.
Perhaps the lid activated the fingerprint sensor just as the system was going to sleep.
This is obviously kde/sddm on X11. Still running ubuntu 24.04 lts with kernel 7.0.0-14-generic.
HTH.