Fingerprint authentication after wake from sleep often not working

Ask Fedora
1

On my Thinkpad P14s with Fedora 41 KDE, fingerprint authentication generally works, but often does not work anymore when resuming from sleep/suspend.

This is the output of journalctl -e, filtered for fprintd:

Mar 10 18:20:40 *** systemd[1]: Starting fprintd.service - Fingerprint Authentication Daemon...
Mar 10 18:20:41 *** fprintd[109349]: Failed to install a sleep delay inhibitor: GDBus.Error:org.freedesktop.login1.OperationInProgress: The operation inhibition has been requested for is already running
Mar 10 18:20:41 *** systemd[1]: Started fprintd.service - Fingerprint Authentication Daemon.
Mar 10 18:20:41 *** 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'
Mar 10 18:20:41 *** fprintd[109349]: Authorization denied to :1.484 to call method 'ListEnrolledFingers' for device 'Goodix MOC Fingerprint Sensor': Not Authorized: net.reactivated.fprint.device.verify
Mar 10 18:33:19 *** systemd[1]: fprintd.service: Deactivated successfully.
Mar 10 18:33:19 *** 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'

It seems to me that the line with ‘authorization denied’ hints to the cause of the problem, but why does it sometimes work and sometimes not?

This is a single-user machine and I have sudo rights.

1 Like
2

Happens to me frequently too:

fprintd[125815]: Device reported an error during verify: Cannot run while suspended.

Is this the same error you get too? Manually starting fprintd temporarily fixes it until the next time i suspend/resume.

3

No, I don’t see this particular message.

I get the impression that it works more reliably now, but when I woke my laptop from sleep right now, fingerprint was not available once again, but there were no errors in the journal:

xxx ~ (main)> journalctl -u fprintd --no-pager
Jul 04 06:15:34 xxx systemd[1]: Starting fprintd.service - Fingerprint Authentication Daemon...
Jul 04 06:15:34 xxx systemd[1]: Started fprintd.service - Fingerprint Authentication Daemon.
Jul 04 06:16:35 xxx systemd[1]: fprintd.service: Deactivated successfully.

Those timetstamps are from a previous wake-up, so there are no fprintd-related entries at all that pertain to the current situation.

4

Yup sounds like a sessio permission issue after suspend, I have seen similar behavior sometimes restarting the fprintd service helps. Hope Fedoraa patches this in a future update.

5

Right now I did get an error message in the journal:

fprintd[39639]: Device reported an error during identify: device was disconnected

This, obviously, is different from the one above.

6

For the past couple of days it’s been working very reliably for me, holding my breath :wink: