Fingerprint reader not working after sleep

Framework Laptop 13 Linux
1

Hi,

I recently received my AMD Framework 13 (7840) on Fedora 40 Workstation, and set up the fingerprint reader. Sometimes when opening the lid and waking it from sleep, the fingerprint doesn’t register on the login screen. I don’t get an error or anything, and I would just use my password. I’ve tried resetting my fingerprint and it doesn’t seem to fix it. I don’t get any errors appearing, it’s as if it was turned off or disabled. However, it does always work when I’m using a sudo command. Any advice would be appreciated!

Thank you.

2 Likes
2

Are you sure this is a Framework issue, but not a Fedora issue?

I’m using the Framework 16 under KDE Platforms 6, and sometimes I get the fingerprint stop working by some reason, seems rarely.

Do you see any error from journald?

3

I’m on a Framework 16 ( 7840HS ) and (rarely) after resume the fingerprint reader doesn’t show on KDE Plasma lock/unlock screen.

If I suspend and resume again straight after, it’s working again.

I see no warnings or errors and in the 7 months I’ve had my FW16, it’s happened less than 10 times

I’m not sure what the issue is and this has been happening with BIOS 3.03 and now 3.04beta ( I don’t remember for 3.02 )

1 Like
4

I actually have this same issue running fedora 40 on my fw13 amd. It is not reproducible with my lenovo thinkpad t15 gen 2 running fedora 40 workstation.

5

I’m experiencing this issue when using my AMD Framework 13 which is running Fedora 40 KDE.

Though, one exception is that it seems to occur some-what consistently if the laptop sleeps for long enough.

Also worth mentioning is that if I sign back in manually then suspend it again, the fingerprint reader will work if I wake it up right after.

1 Like
6

Pretty much same behavior for me too!

7

Here are some of the things that I get after running “journalctl -b | grep fprintd” in the terminal:

Oct 10 19:22:21 framework-13 systemd[1]: Starting fprintd.service - Fingerprint Authentication Daemon…
Oct 10 19:22:22 framework-13 systemd[1]: Started fprintd.service - Fingerprint Authentication Daemon.
Oct 10 19:22:22 framework-13 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg=‘unit=fprintd comm=“systemd” exe=“/usr/lib/systemd/systemd” hostname=? addr=? terminal=? res=success’
Oct 10 19:22:48 framework-13 fprintd[36593]: Device reported an error during verify: Cannot run while suspended.
Oct 10 19:22:48 framework-13 gdm-fingerprint][36615]: pam_fprintd(gdm-fingerprint:auth): ReleaseDevice failed: Release failed with error: The device is still busy with another operation, please try again later.
Oct 10 19:49:09 framework-13 systemd[1]: fprintd.service: Deactivated successfully.
Oct 10 19:49:09 framework-13 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg=‘unit=fprintd comm=“systemd” exe=“/usr/lib/systemd/systemd” hostname=? addr=? terminal=? res=success’
Oct 10 19:50:06 framework-13 systemd[1]: Starting fprintd.service - Fingerprint Authentication Daemon…
Oct 10 19:50:06 framework-13 systemd[1]: Started fprintd.service - Fingerprint Authentication Daemon.
Oct 10 19:50:06 framework-13 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg=‘unit=fprintd comm=“systemd” exe=“/usr/lib/systemd/systemd” hostname=? addr=? terminal=? res=success’

It does appear to be an issue at times when it goes to sleep.

8

Did you ever get this figured out? I’m on Ubuntu 24.10 and I am having the same issue. Terminal returns a nearly identical report on mine when I run “journalctl -b | grep fprintd” as well.

Edit: I’m running a FW13 AMD 7840U

9

Unfortunately, not yet. I have a Framework support ticket opened up and its been escalated. Hopefully, they’ll respond with a solution sometime this week!

10

Since I last posted (2024-09-14 ), there have been numerous updates since then, I’ve suspended/hibernated my system countless times and the issue hasn’t happened yet, so I think it was a software issue for me that later got fixed ( maybe KDE Plasma 6.1.5, stabilized on Gentoo on 2024-09-21 ).

I’m thinking maybe it wasn’t a hardware or BIOS issue ( for me at least on FW16 )

11

I upgraded to Fedora 41 Workstation hoping it would somehow fix itself, but the fingerprint login still persisted. I did a clean install of 41 as recommended by support, and it seemed to work. However, when adding certain or many Gnome extensions, the fingerprint login screen started to become slower. So maybe it’s possible the extensions caused the issue? I don’t recall what extensions I originally had, but it around 12 or so. I just use 6 on the fresh install now.

Edit: Confirming it was actually the extensions that caused the fingerprint issues in my case as I was able to recreate the same issue. If adding extensions, do so one at a time to see if affects the login. It’ll tend to authenticate slower or might not just work at all.