[RESPONDED] Fingerprints delete after one failed try

Framework Laptop Linux
#1

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 ~]$
#2

Let’s start by reinstalling fprintd and fprintd-pam. Reboot. Then try:

  • fprintd-delete $USER
  • fprintd-enroll
    (And if that went well)
  • fprintd-verify

Next:

sudo authselect enable-feature with-fingerprint

sudo authselect apply-changes

#3

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 ~]$
#4

Anything else I can try or do I have to reinstall fedora?

#5

I just set up fingerprint reader on Fedora 37 today. I think a fresh install is worthwhile.

#6

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)
#7

Here is an updated command got the port to run but new error appears

[elizam343@sueno ~]$ systemctl status fprintd.service
○ fprintd.service - Fingerprint Authentication Daemon
     Loaded: loaded (/usr/lib/systemd/system/fprintd.service; enabled; preset: >
     Active: inactive (dead) since Sat 2023-03-11 14:38:38 EST; 33s ago
   Duration: 51.086s
       Docs: man:fprintd(1)
    Process: 5321 ExecStart=/usr/libexec/fprintd (code=exited, status=0/SUCCESS)
   Main PID: 5321 (code=exited, status=0/SUCCESS)
        CPU: 125ms

Mar 11 14:37:47 sueno systemd[1]: Started fprintd.service - Fingerprint Authent>
Mar 11 14:37:47 sueno fprintd[5321]: libusb: error [udev_hotplug_event] ignorin>
Mar 11 14:37:47 sueno fprintd[5321]: libusb: error [udev_hotplug_event] ignorin>
Mar 11 14:37:47 sueno fprintd[5321]: libusb: error [udev_hotplug_event] ignorin>
Mar 11 14:37:58 sueno fprintd[5321]: libusb: error [udev_hotplug_event] ignorin>
Mar 11 14:37:58 sueno fprintd[5321]: libusb: error [udev_hotplug_event] ignorin>
Mar 11 14:38:03 sueno fprintd[5321]: Failed to garbage collect duplicate print,>
Mar 11 14:38:08 sueno fprintd[5321]: libusb: error [udev_hotplug_event] ignorin>
Mar 11 14:38:08 sueno fprintd[5321]: libusb: error [udev_hotplug_event] ignorin>
Mar 11 14:38:38 sueno systemd[1]: fprintd.service: Deactivated successfully.
lines 1-19/19 (END)
#8

Let’s give this appimage a shot. I have been in touch with the creator in the past, it has helped a lot in these situations.

#9

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.

#10

Happy to help. Let’s take a look at some logs for any indications of what might be happening.

sudo dmesg | grep authentication

journalctl | grep authentication

sudo dmesg | grep keyring

journalctl | grep keyring

Let’s take a look at the output of those, and see what if anything stands out.

#11

The only thing I noticed was from running the command journalctl authentication i got this failure

Mar 13 00:23:36 sueno realmd[1644]: GLib-GIO: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)
Mar 13 00:24:40 sueno gdm-password][1784]: pam_unix(gdm-password:auth): authentication failure; logname= uid=0 euid=0 tty=/dev/tty1 ruser= rhost=  user=elizam343
Mar 13 00:24:40 sueno audit[1784]: USER_AUTH pid=1784 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:authentication grantors=? acct="elizam343" exe="/usr/libexec/gdm-session-worker" hostname=sueno addr=? terminal=/dev/tty1 res=failed'

I was also able to find this

Mar 12 03:28:15 sueno wpa_supplicant[1202]: wlp166s0: CTRL-EVENT-EAP-STARTED EAP authentication started
Mar 12 03:28:16 sueno wpa_supplicant[1202]: wlp166s0: CTRL-EVENT-EAP-FAILURE EAP authentication failed
Mar 12 03:28:29 sueno wpa_supplicant[1202]: wlp166s0: CTRL-EVENT-EAP-STARTED EAP authentication started
Mar 12 03:28:31 sueno wpa_supplicant[1202]: wlp166s0: CTRL-EVENT-EAP-FAILURE EAP authentication failed
Mar 12 03:28:49 sueno wpa_supplicant[1202]: wlp166s0: CTRL-EVENT-EAP-STARTED EAP authentication started
Mar 12 03:28:50 sueno wpa_supplicant[1202]: wlp166s0: CTRL-EVENT-EAP-FAILURE EAP authentication failed
Mar 12 03:29:02 sueno wpa_supplicant[1202]: wlp166s0: CTRL-EVENT-EAP-STARTED EAP authentication started
Mar 12 03:29:03 sueno wpa_supplicant[1202]: wlp166s0: CTRL-EVENT-EAP-FAILURE EAP authentication failed
Mar 12 03:37:41 sueno audit[4909]: USER_AUTH pid=4909 uid=0 auid=1000 ses=2 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:authentication grantors=pam_fprintd acct="elizam343" exe="/usr/libexec/gdm-session-worker" hostname=sueno addr=? terminal=/dev/tty1 res=success'
Mar 12 03:38:08 sueno wpa_supplicant[1202]: wlp166s0: CTRL-EVENT-EAP-STARTED EAP authentication started
Mar 12 03:38:09 sueno wpa_supplicant[1202]: wlp166s0: CTRL-EVENT-EAP-FAILURE EAP authentication failed
Mar 12 03:38:21 sueno wpa_supplicant[1202]: wlp166s0: CTRL-EVENT-EAP-STARTED EAP authentication started
Mar 12 03:38:22 sueno wpa_supplicant[1202]: wlp166s0: CTRL-EVENT-EAP-FAILURE EAP authentication failed
Mar 12 03:39:19 sueno wpa_supplicant[1202]: wlp166s0: CTRL-EVENT-EAP-STARTED EAP authentication started
Mar 12 03:39:19 sueno wpa_supplicant[1202]: wlp166s0: CTRL-EVENT-EAP-SUCCESS EAP authentication completed successfully
Mar 12 03:47:12 sueno audit[6805]: USER_AUTH pid=6805 uid=1000 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:authentication grantors=pam_fprintd acct="elizam343" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'

Other than that the other commands I did not see anything notable were the test didnt run or pass

#12

Nothing turned up on these by chance?

sudo dmesg | grep keyring

journalctl | grep keyring
#13

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.
#14

Silly question, but is auto-login enabled in your user settings by chance?

#15

No I have it disabled

#16

image
image760×402 24.2 KB

#17

Feeling like something tweaked something along the way. As I see in your log entry we’re definitely getting errors.

We can try:

sudo dnf reinstall gnome-shell gnome-session gnome-keyring

Reboot, if that didn’t fix anything, we’re going to need to dig into the logs a bit deeper to see if anything stands out.

journalctl -xe
#18

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.
#19

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.