I am currently running Fedora 37. When I did a fresh install of fedora. The fingerprint sensor seemed to work. I was able to register my fingerprints no problem. But after I tried to use to my fingerprint to login it would say failed to match and when I logged in to settings the fingerprint was disabled and deleted. I looked at the previous forums for fixing the fingerprint and some commands do not work or do not give the desired output. When I run status of fprintd this is the message I get.
[elizam343@sueno ~]$ systemctl status fprintd
○ fprintd.service - Fingerprint Authentication Daemon
Loaded: loaded (/usr/lib/systemd/system/fprintd.service; static)
Active: inactive (dead)
Docs: man:fprintd(1)
Jan 26 08:25:17 sueno fprintd[3730]: Capture sample failed, result: 0xc0
Jan 26 08:25:20 sueno fprintd[3730]: Capture sample failed, result: 0xc0
Jan 26 08:25:34 sueno fprintd[3730]: libusb: error [udev_hotplug_event] ignorin>
Jan 26 08:25:34 sueno fprintd[3730]: libusb: error [udev_hotplug_event] ignorin>
Jan 26 08:25:38 sueno fprintd[3730]: Deleted stored finger 7 for user elizam343>
Jan 26 08:25:46 sueno fprintd[3730]: libusb: error [udev_hotplug_event] ignorin>
Jan 26 08:25:46 sueno fprintd[3730]: libusb: error [udev_hotplug_event] ignorin>
Jan 26 08:25:58 sueno fprintd[3730]: libusb: error [udev_hotplug_event] ignorin>
Jan 26 08:25:58 sueno fprintd[3730]: libusb: error [udev_hotplug_event] ignorin>
Jan 26 08:26:28 sueno systemd[1]: fprintd.service: Deactivated successfully.
[elizam343@sueno ~]$
I did everything uninstall and reinstall fprintd and fprintd-pam and it took me back to the fingerprint deleting after verifying
[elizam343@sueno ~]$ fprintd-verify
Using device /net/reactivated/Fprint/Device/0
ListEnrolledFingers failed: GDBus.Error:net.reactivated.Fprint.Error.NoEnrolledPrints: Failed to discover prints
[elizam343@sueno ~]$
Hey sorry I never got back to you I had to deal with some stuff. I did a fresh install on fedora and for status fprintd it continues to mark as inactive. I saw the new installtion process that was posted and when editing the fprintd file it failed.
[elizam343@sueno ~]$ systemctl status fprintd
○ fprintd.service - Fingerprint Authentication Daemon
Loaded: loaded (/usr/lib/systemd/system/fprintd.service; enabled; preset: >
Active: inactive (dead) since Sat 2023-03-11 14:25:14 EST; 36s ago
Duration: 58.495s
Docs: man:fprintd(1)
Process: 1000 ExecStart=/usr/libexec/fprintd (code=exited, status=0/SUCCESS)
Main PID: 1000 (code=exited, status=0/SUCCESS)
CPU: 77ms
Mar 11 14:24:15 sueno systemd[1]: Starting fprintd.service - Fingerprint Authen>
Mar 11 14:24:16 sueno systemd[1]: Started fprintd.service - Fingerprint Authent>
Mar 11 14:24:16 sueno fprintd[1000]: libusb: error [udev_hotplug_event] ignorin>
Mar 11 14:24:16 sueno fprintd[1000]: libusb: error [udev_hotplug_event] ignorin>
Mar 11 14:25:14 sueno systemd[1]: fprintd.service: Deactivated successfully.
lines 1-14/14 (END)
Thank you so much. It almost worked. I am now able to use fingerprints and they get saved. Now what I mean by almost worked is When I log into my computer I get the message “authentication required the login keyring did not get unlocked” Do you have any idea I tried to see if the forum you sent had an answer and it appears that someone had the issue as mine but no one answered them.
Actually something did pop up on journalctl grep keyring I just missed it by chance
Mar 15 17:59:07 sueno systemd[1813]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-1964.scope - Application launched by gnome-session-binary.
Mar 15 17:59:07 sueno systemd[1813]: app-gnome-gnome\x2dkeyring\x2dssh-1960.scope: Couldn't move process 1960 to requested cgroup '/user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome-gnome\x2dkeyring\x2dssh-1960.scope': No such process
Mar 15 17:59:07 sueno systemd[1813]: app-gnome-gnome\x2dkeyring\x2dssh-1960.scope: Failed to add PIDs to scope's control group: No such process
Mar 15 17:59:07 sueno systemd[1813]: app-gnome-gnome\x2dkeyring\x2dssh-1960.scope: Failed with result 'resources'.
Mar 15 17:59:07 sueno systemd[1813]: Failed to start app-gnome-gnome\x2dkeyring\x2dssh-1960.scope - Application launched by gnome-session-binary.
reinstalling sadly didn’t work I did reinstall after because there was an error while installing
(1/3): gnome-session-43.0-1.fc37.x86_64.rpm 1.5 MB/s | 408 kB 00:00
(2/3): gnome-shell-43.3-1.fc37.x86_64.rpm 1.9 MB/s | 1.7 MB 00:00
[MIRROR] gnome-keyring-42.1-2.fc37.x86_64.rpm: Curl error (28): Timeout was reached for http://mirror.arizona.edu/fedora/linux/releases/37/Everything/x86_64/os/Packages/g/gnome-keyring-42.1-2.fc37.x86_64.rpm [Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds]
(3/3): gnome-keyring-42.1-2.fc37.x86_64.rpm 24 kB/s | 897 kB 00:37
This what appeared in the logs
[elizam343@sueno ~]$ journalctl -xe
░░Defined-By: systemd░░Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel░░░░A start job for unit UNIT has begun execution.░░░░The job identifier is 732.
Mar 17 12:20:47 sueno systemd[1800]: Started gnome-terminal-server.service - GN>░░ Subject: A start job for unit UNIT has finished successfully░░Defined-By: systemd░░Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel░░░░A start job for unit UNIT has finished successfully.░░░░The job identifier is 732.
Mar 17 12:20:47 sueno gnome-shell[1976]: meta_window_set_stack_position_no_sync>
Mar 17 12:20:47 sueno systemd[1800]: Started vte-spawn-a087ada6-f7e3-40f3-acfa->░░ Subject: A start job for unit UNIT has finished successfully░░Defined-By: systemd░░Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel░░░░A start job for unit UNIT has finished successfully.░░░░The job identifier is 749.lines 3393-3415/3415 (END)░░Defined-By: systemd░░Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel░░░░A start job for unit UNIT has begun execution.░░░░The job identifier is 732.
Mar 17 12:20:47 sueno systemd[1800]: Started gnome-terminal-server.service - GNOME Terminal Server.
░░ Subject: A start job for unit UNIT has finished successfully░░Defined-By: systemd░░Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel░░░░A start job for unit UNIT has finished successfully.░░░░The job identifier is 732.
Mar 17 12:20:47 sueno gnome-shell[1976]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed
Mar 17 12:20:47 sueno systemd[1800]: Started vte-spawn-a087ada6-f7e3-40f3-acfa-fbc37ef79546.scope - VTE child process 4041 launched by gnome-terminal-server process 4023.
░░ Subject: A start job for unit UNIT has finished successfully░░Defined-By: systemd░░Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel░░░░A start job for unit UNIT has finished successfully.░░░░The job identifier is 749.
Defined-By: systemd░░Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel░░░░A start job for unit UNIT has begun execution.░░░░The job identifier is 732.
Mar 17 12:20:47 sueno systemd[1800]: Started gnome-terminal-server.service - GNOME Terminal Server.
░░ Subject: A start job for unit UNIT has finished successfully░░Defined-By: systemd░░Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel░░░░A start job for unit UNIT has finished successfully.░░░░The job identifier is 732.
Mar 17 12:20:47 sueno gnome-shell[1976]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed
Mar 17 12:20:47 sueno systemd[1800]: Started vte-spawn-a087ada6-f7e3-40f3-acfa-fbc37ef79546.scope - VTE child process 4041 launched by gnome-terminal-server process 4023.
░░ Subject: A start job for unit UNIT has finished successfully░░Defined-By: systemd░░Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel░░░░A start job for unit UNIT has finished successfully.░░░░The job identifier is 749.
We may be edging near clean installation territory. I have been unable to duplicate this on multiple Framework machines myself. My guess is something was goofed up somewhere with the keyring and we need to start off with a fresh install.