I have been having this issue since I got my Laptop 13. When resuming from sleep, contact is often lost with the fingerprint reader (more rarely than 1/2 times but more often than 1/8). I haven’t been able to find a pattern to when it happens and the only way I have found to make it work again is rebooting the computer.
When this happens, hyprlock seems to freeze for a couple of seconds upon returning from sleep and afterwards, unlocking with fingerprint always fails. After unlocking with password, running fprintd-list -a returns No devices available. After a reboot, it works perfectly fine again and the above command returns:
found 1 devices
Device at /net/reactivated/Fprint/Device/0
Using device /net/reactivated/Fprint/Device/0
I have tried following a bunch of tips I found online without any results. Does anyone here know if my hardware might be broken or if I simply have a bad config somewhere?
I am curious. I setup SDDM with fingerprint reading, and man, this is all over the map. Did you experience same stuff? If not, how are you using it? I am super curious!!
yes, fingerprint is registered and works, but…
one has to first register focus in the password text box and press enter
once a character is entered, fingerprints are then readable, read, and login happens!
That is fricking weird, but seems to be state of the art. OR…
My main login screen where I can choose Niri or Hyprland etc, now lets me type in a password fine and once I do that, it then flashes me the message to place my finger on the fingerprint reader. Which then works.
So this is also a WTF crazy and would obviously never be an acceptable flow if think about it. Why is enabling the fingerprint reader not just smooth as butter and workable with PAM! Is PAM really that clunky???
Having the same issue here. At times fprintd seems to also prevent sleep, but usually on wake up the laptop will lock up at various points during the resume. Sometimes I get a black screen, sometimes the GUI is up but frozen, etc etc. Seems to always be the fingerprint reader causing this issue. If this happens, fprintd will invariably prevent shutdown, such that daily I have to emergency sync and hold the power button down or it will take 30 minutes or more to shutdown.
During this time fwupd will also timeout with `Failed to connect to daemon: Error calling StartServiceByName for org.freedesktop.fwupd: Timeout was reached`
Using the latest Arch and bios version.
Next time this happens on resume I will capture the dmesg output.
same issue here for me on nixos with 6.18.1. i got a workaround to not have to reboot every time the driver disconnects, by killing fprintd before sleep, and then on resume unbinding the the xHCI controller and rebinding it which starts fprintd automatically. It’s lags hyprlock but at least i can use it for everything else after that
Finally got around to doing some searching in journalctl and found some suspicious messages. They led me to posts like this one, making me more certain that this is not a hardware issue or directly related to Arch. Then I found this post on here and the script shared there seems to do the trick for me! It would be great to figure out what actually causes this as it seems to be a problem on a pretty low level of the OS but I really don’t have time to dig any further.