[SOLVED] fprintd stopped working

Der Chefkoch · 2021-07-04 19:47:21

Out of the blue - I guess after some update - the fingerprint sensor on my below described Laptop stopped working. This is annoying as sudo and other authentications would first invoke the fingerprint reader.

Here is the log:

Jul 04 21:42:04 arch systemd[1]: Starting Fingerprint Authentication Daemon...
Jul 04 21:42:04 arch kernel: audit: type=1334 audit(1625427724.181:171): prog-id=47 op=LOAD
Jul 04 21:42:04 arch fprintd[8711]: /usr/lib/fprintd: symbol lookup error: /usr/lib/fprintd: undefined symbol: fp_device_has_feature, version LIBFPRINT_2.0.0
Jul 04 21:42:04 arch systemd[1]: fprintd.service: Main process exited, code=exited, status=127/n/a
Jul 04 21:42:04 arch systemd[1]: fprintd.service: Failed with result 'exit-code'.
Jul 04 21:42:04 arch systemd[1]: Failed to start Fingerprint Authentication Daemon.
Jul 04 21:42:04 arch audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=fprintd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Jul 04 21:42:04 arch kernel: audit: type=1130 audit(1625427724.221:172): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=fprintd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Jul 04 21:42:04 arch audit: BPF prog-id=47 op=UNLOAD
Jul 04 21:42:04 arch kernel: audit: type=1334 audit(1625427724.561:173): prog-id=47 op=UNLOAD
Jul 04 21:42:18 arch albert.desktop[2212]: 21:42:18 [info:firefox] Start indexing Firefox bookmarks.
Jul 04 21:42:18 arch albert.desktop[2212]: 21:42:18 [info:firefox] Indexed 189 Firefox bookmarks.
Jul 04 21:42:24 arch kernel: x86/split lock detection: #AC: CJobMgr::m_Work/2837 took a split_lock trap at address: 0xe7516263
Jul 04 21:42:29 arch dbus-daemon[1332]: [system] Failed to activate service 'net.reactivated.Fprint': timed out (service_start_timeout=25000ms)
Jul 04 21:42:29 arch sudo[8710]: pam_fprintd(sudo:auth): GetDevices failed: Die Wartezeit für die Verbindung ist abgelaufen
Jul 04 21:42:29 arch kernel: x86/split lock detection: #AC: CJobMgr::m_Work/2880 took a split_lock trap at address: 0xe7516263
Jul 04 21:42:29 arch kernel: x86/split lock detection: #AC: CJobMgr::m_Work/2837 took a split_lock trap at address: 0xe7516263

How to interpret this error message?

Cheers

Last edited by Der Chefkoch (2021-07-06 18:38:03)

seth · 2021-07-04 20:33:53

Smells like partial upgrade.

pacman -Qs fprint

Der Chefkoch · 2021-07-05 04:40:14

seth wrote:

Smells like partial upgrade.
pacman -Qs fprint

here we go

local/fprintd 1.92.0-1 (fprint)
    D-Bus service to access fingerprint readers
local/libfprint-2-tod1-xps9300-bin 0.0.6-2 (fprint)
    Proprietary driver for the fingerprint reader on the Dell XPS 13 9300 - direct from Dell's Ubuntu repo
local/libfprint-tod-git 1.90.5+tod1-1 (fprint)
    Library for fingerprint readers - TOD version

seth · 2021-07-05 05:29:14

You're using two (patched, I assume) libfprint libraries from the AUR and though not updated there, they seem too old for the latest fprintd.
You either need to downgrade fprintd, update those packages "somehow" or use libfprint from the repos.

OfficerK · 2021-07-05 11:59:28

Hi,

after my last system upgrade on Friday my fingerprint reader also stopped working.
I downgraded from

 fprintd v1.92.0-1

to

 frpintd v1.90.6-1

It is working for me again, now.

Cheers

Der Chefkoch · 2021-07-06 18:37:40

Thanks for that, rolling back fprintd did work. Although it seems fprintd now does not start at bootup.

aegis · 2021-07-06 23:43:57

seth wrote:

You're using two (patched, I assume) libfprint libraries from the AUR and though not updated there, they seem too old for the latest fprintd.
You either need to downgrade fprintd, update those packages "somehow" or use libfprint from the repos.

I have been having the same problem. I uninstalled the libfprint from AUR and re-installed fprintd which then pulled libfprint from the repos. Thanks.

Der Chefkoch · 2021-07-07 18:13:54

aegis wrote:

seth wrote:
You're using two (patched, I assume) libfprint libraries from the AUR and though not updated there, they seem too old for the latest fprintd.
You either need to downgrade fprintd, update those packages "somehow" or use libfprint from the repos.
I have been having the same problem. I uninstalled the libfprint from AUR and re-installed fprintd which then pulled libfprint from the repos. Thanks.

Good for you if that works, on my device this does not work unless I use the AUR libraries.

nihil21 · 2021-07-13 23:12:29

Der Chefkoch wrote:

Thanks for that, rolling back fprintd did work. Although it seems fprintd now does not start at bootup.

I'm having the same problem: after downgrading fprintd to version 1.90.6-1, the fingerprint worked again but the service didn't start at boot. To solve this problem, I had to edit the file /usr/lib/systemd/system/fprintd.service and append at the end the following lines:

[Install]
WantedBy=multi-user.target

Finally, I issued the command:

sudo systemctl enable fprintd.service

and now it starts at boot.

Der Chefkoch · 2021-07-17 11:47:16

nihil21 wrote:

Der Chefkoch wrote:
Thanks for that, rolling back fprintd did work. Although it seems fprintd now does not start at bootup.
I'm having the same problem: after downgrading fprintd to version 1.90.6-1, the fingerprint worked again but the service didn't start at boot. To solve this problem, I had to edit the file /usr/lib/systemd/system/fprintd.service and append at the end the following lines:
[Install]
WantedBy=multi-user.target
Finally, I issued the command:
sudo systemctl enable fprintd.service
and now it starts at boot.

Well the service starts at boot, however it randomly asks for either password or the fingerprint in my case. Curious

astadnik · 2021-08-14 08:49:34

It seems to me that the fingerprint is suspended somehow, and cannot start fast enough.

journalctl -u fprintd.service

shows a lot of these:

сер 14 11:34:39 astadnik systemd[1]: Starting Fingerprint Authentication Daemon...
сер 14 11:34:40 astadnik systemd[1]: Started Fingerprint Authentication Daemon.
сер 14 11:35:22 astadnik systemd[1]: fprintd.service: Deactivated successfully.
сер 14 11:35:22 astadnik systemd[1]: fprintd.service: Consumed 1.215s CPU time.

Also, if I try to trigger fingerprint, for example, for sudo, first it would ask for a password, but if I input it incorrectly, the next time it would ask for a fingerprint. If shortly after that I open a new console, and try to run smth with sudo again, this time it would run fingerprint immediately, I assume, because it is in "active" state. I think the delay before asking for a password should be bigger, or the startup time of fprint should be made smaller somehow. However, I can't find any info regarding this.

seth · 2021-08-14 14:51:39

systemctl status fprintd

You're probably relying on the dbus activation and don't have the service enabled?

nihil21 · 2021-10-01 10:24:10

I've found a better workaround: the `libfprint-tod-git` library has been updated upstream, but the AUR package is still out-of-date. Therefore: I downloaded the PKGBUILD file, compiled it with `makepkg --nocheck` and installed it with `pacman -U`. Now it works with the most recent version of `fprintd`.

Arch Linux

#1 2021-07-04 19:47:21

[SOLVED] fprintd stopped working

#2 2021-07-04 20:33:53

Re: [SOLVED] fprintd stopped working

#3 2021-07-05 04:40:14

Re: [SOLVED] fprintd stopped working

#4 2021-07-05 05:29:14

Re: [SOLVED] fprintd stopped working

#5 2021-07-05 11:59:28

Re: [SOLVED] fprintd stopped working

#6 2021-07-06 18:37:40

Re: [SOLVED] fprintd stopped working

#7 2021-07-06 23:43:57

Re: [SOLVED] fprintd stopped working

#8 2021-07-07 18:13:54

Re: [SOLVED] fprintd stopped working

#9 2021-07-13 23:12:29

Re: [SOLVED] fprintd stopped working

#10 2021-07-17 11:47:16

Re: [SOLVED] fprintd stopped working

#11 2021-08-14 08:49:34

Re: [SOLVED] fprintd stopped working

#12 2021-08-14 14:51:39

Re: [SOLVED] fprintd stopped working

#13 2021-10-01 10:24:10

Re: [SOLVED] fprintd stopped working

Board footer