Which release version?
(if rolling release without a release version, skip this question)
24.04
(If rolling release, last date updated?)
Which kernel are you using?
6.17.0-19-generic
Which BIOS version are you using?
03.18
Which Framework Laptop 13 model are you using? (AMD Ryzen™ AI 300 Series, AMD Ryzen™ 7040 Series, Intel® Core™ Ultra Series 1, 13th Gen Intel® Core™ , 12th Gen Intel® Core™, 11th Gen Intel® Core™)
AMD 7040
I’ve had this problem since the beginning but only conjured the bother to post this now. The fingerprint sensor sometimes works and sometimes doesn’t and as far as I can see it’s completely unpredictable. Surely I’m not the only one with this problem?
if you have not already done so, try reaching out to framework support to see what they suggest.
For this forum thread, it might help if you describe in a little more detail what “not working unpredictably” is like. Does it not work from booting until the next reboot? Does it stop and then start working again during the same desktop session? Can you logout and log back in to get it working again? etc.
On my device, I don’t like the fact that there is a time window over which the finger print sensor accepts input; however, this is the intended behavior. If it times out, there is a message to that effect and I generally just “hit enter” with a blank password to reset the finger print timer. After doing that, the finger print sensor does work. The finger print sensor also works reliably for me with for cli commands (i.e. sudo) - not sure if there is a time out there as well.
For the record, I’m using kde with X11/sddm. What desktop environment are you using? Gnome, wayland or X11?
EDIT: in other words, you might want to try searching ubuntu forums for your device/environment as well as any troubleshooting section that might be associated with the instructions to set up the finger print sensor. For kubuntu 24.04 (my distribution) the finger print sensor did not work without my intervention to enable it.
I have had the same problem. To add a bit of detail, it almost never works the first time after it has been asleep for a while and give the error ‘you have tried too many times’ and requires entering the password. When it hasn’t been in sleep mode very long, it usually works, and it may always work except that it is pretty sensitive to the exact location and angle of the finger. I improved reliability by rerecording my fingerprint now that I know how I usually put my finger down.
As soon as I wrote this, I have not been able to replicate the problem – placing my finger carefully, even when the PC has been asleep, will log me in.
Sorry haven’t had much time to deal with this but thank you for your advice. I’ll follow it when I get a chance.
Regarding more details on the behaviour, it definitely “stop and then start working again during the same desktop session” to quote you. I’ve actually noticed a perfect correlation recently; the finger-print reader works if and only if , when I open the laptop (waking it from sleep), there’s a caret in the password box. It still seems random, whenever I open the laptop, whether there would be a caret in the password box or not, but the finger-print sensor works when there’s a caret in the password box, and doesn’t when there isn’t a caret there. This feels like the sort of thing a dedicated Ubuntu contributor would be able to figure out. I’m a dev myself but I just really really don’t have the time/energy to patch this. Unless Framework decides to hire me LOL.
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.