Fingerprint instability on Fedora 42 KDE (Thinkpad X1 Yoga Gen6)

I have recently purchased a refurbished Thinkpad X1 Yoga gen 6 (Intel i7 11th gen), replaced the SSD and installed Fedora 42 KDE - this macine and setup is very nice, and everything works, including fingerprint sensor and firmware updates in Discover :slight_smile:

The fingerprint reader sometimes stops working, though. I know the integration to KDE is not perfect, but I have also run into stability / consistency issues with fprintd. When it stops working, I see two sensors in the following output (after reboot or restart of fprintd I see only one again):

~ ❯ fprintd-list jeppe
found 2 devices
Device at /net/reactivated/Fprint/Device/1
Device at /net/reactivated/Fprint/Device/2
Using device /net/reactivated/Fprint/Device/1
Fingerprints for user jeppe on Synaptics Sensors (press):
 - #0: left-index-finger
 - #1: right-index-finger
Using device /net/reactivated/Fprint/Device/2
Fingerprints for user jeppe on Synaptics Sensors (press):
 - #0: left-index-finger
 - #1: right-index-finger

…and I see this in the journal log:

maj 20 07:48:18 x1yoga systemd[1]: Started fprintd.service - Fingerprint Authentication Daemon.
maj 20 09:54:21 x1yoga fprintd[9916]: Async command sending failed: USB error on device 06cb:00fc : No such device (it may have been disconnected) [-4]
maj 20 09:54:46 x1yoga fprintd[9916]: Verification was in progress, stopping it
maj 20 10:04:37 x1yoga fprintd[9916]: Authorization denied to :1.258 to call method 'Claim' for device 'Synaptics Sensors': Device was already claimed

When this has happened, I can restart the fprintd service, and fix it. The service does not stop nicely, though, systemd kills it, because the stop-sigterm times out.

I do use suspend/wake, and I suspect it plays a role - but most of the time the suspend/wake works well, and I can unlock KDE with my fingerprint.

Any clues as to what is going on, and potentially a fix/workaround?

/Jaybe