[SOLVED] Fedora 37 fingerprint not enrolling

Framework Laptop 13 Linux
1

Hello all

I was running Windows 10/11 and had no issues whatsoever with the fingerprint reader, but on a fresh install of Fedora 37 it just will not enroll a fingerprint. I did another fresh install and all I’ve done to this one is sudo dnf upgrade -y, but still no luck. Here’s the output of trying to do this manually from the terminal:

[afranco@localhost-live Code]$ fprintd-enroll -f right-index-finger afranco
Using device /net/reactivated/Fprint/Device/0
Enrolling right-index-finger finger.
Enroll result: enroll-duplicate
[afranco@localhost-live Code]$ 
[afranco@localhost-live Code]$ systemctl status fprintd
● fprintd.service - Fingerprint Authentication Daemon
     Loaded: loaded (/usr/lib/systemd/system/fprintd.service; static)
     Active: active (running) since Tue 2022-12-27 22:24:38 CST; 59s ago
       Docs: man:fprintd(1)
   Main PID: 5233 (fprintd)
      Tasks: 6 (limit: 38209)
     Memory: 1.9M
        CPU: 91ms
     CGroup: /system.slice/fprintd.service
             └─5233 /usr/libexec/fprintd

Dec 27 22:24:38 localhost-live fprintd[5233]: libusb: error [udev_hotplug_event] ignoring udev action change
Dec 27 22:24:38 localhost-live systemd[1]: Started fprintd.service - Fingerprint Authentication Daemon.
Dec 27 22:24:38 localhost-live fprintd[5233]: libusb: error [udev_hotplug_event] ignoring udev action change
Dec 27 22:25:01 localhost-live fprintd[5233]: libusb: error [udev_hotplug_event] ignoring udev action change
Dec 27 22:25:01 localhost-live fprintd[5233]: libusb: error [udev_hotplug_event] ignoring udev action change
Dec 27 22:25:09 localhost-live fprintd[5233]: libusb: error [udev_hotplug_event] ignoring udev action change
Dec 27 22:25:09 localhost-live fprintd[5233]: libusb: error [udev_hotplug_event] ignoring udev action change
Dec 27 22:25:23 localhost-live fprintd[5233]: libusb: error [udev_hotplug_event] ignoring udev action change
Dec 27 22:25:23 localhost-live fprintd[5233]: libusb: error [udev_hotplug_event] ignoring udev action change
Dec 27 22:25:30 localhost-live fprintd[5233]: Failed to garbage collect duplicate print, cannot continue with enroll: Passed (print) data is not valid.
[afranco@localhost-live Code]$ 
[afranco@localhost-live Code]$



I’ve tried the libfprint_delete_device_prints.py script, but that errors with the following:

[afranco@localhost-live Code]$ sudo python3 libfprint_delete_device_prints.py
<__gi__.FpiDeviceGoodixMoc object at 0x7f5675487080 (FpiDeviceGoodixMoc at 0x56520d97b140)>
goodixmoc
UID036745B2_XXXX_MOC_B0
libusb: error [udev_hotplug_event] ignoring udev action change
libusb: error [udev_hotplug_event] ignoring udev action change
libusb: error [udev_hotplug_event] ignoring udev action change
libusb: error [udev_hotplug_event] ignoring udev action change

(process:6211): libfprint-ERROR **: 22:34:39.414: parse fingerlist error
Trace/breakpoint trap
[afranco@localhost-live Code]$ 
[afranco@localhost-live Code]$ 
[afranco@localhost-live Code]$ sudo python3 libfprint_delete_device_prints.py -d
<__gi__.FpiDeviceGoodixMoc object at 0x7f2fbce78980 (FpiDeviceGoodixMoc at 0x5635f2402140)>
goodixmoc
UID036745B2_XXXX_MOC_B0
libusb: error [udev_hotplug_event] ignoring udev action change
libusb: error [udev_hotplug_event] ignoring udev action change
libusb: error [udev_hotplug_event] ignoring udev action change
libusb: error [udev_hotplug_event] ignoring udev action change

(process:6240): libfprint-ERROR **: 22:34:42.997: parse fingerlist error
Trace/breakpoint trap
[afranco@localhost-live Code]$ 
[afranco@localhost-live Code]$ 
[afranco@localhost-live Code]$



And here’s the output of lsusb:

[afranco@localhost-live Code]$ lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 27c6:609c Shenzhen Goodix Technology Co.,Ltd. Goodix USB2.0 MISC
Bus 003 Device 003: ID 8087:0032 Intel Corp. AX210 Bluetooth
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 090c:3350 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) USB DISK
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 004: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter
Bus 006 Device 006: ID 0424:5744 Microchip Technology, Inc. (formerly SMSC) Hub
Bus 006 Device 005: ID 0424:5744 Microchip Technology, Inc. (formerly SMSC) Hub
Bus 006 Device 003: ID 0bda:0413 Realtek Semiconductor Corp. Dell dock
Bus 006 Device 002: ID 0bda:0487 Realtek Semiconductor Corp. Dell dock
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 004: ID 413c:b06e Dell Computer Corp. Dell dock
Bus 005 Device 011: ID 413c:b06f Dell Computer Corp. Dell dock
Bus 005 Device 008: ID 0bda:402e Realtek Semiconductor Corp. USB Audio
Bus 005 Device 012: ID 413c:301d Dell Computer Corp. Dell Universal Receiver
Bus 005 Device 009: ID 413c:a506 Dell Computer Corp. DELL PROFESSIONAL SOUND BAR AE515
Bus 005 Device 006: ID 0424:2744 Microchip Technology, Inc. (formerly SMSC) Hub
Bus 005 Device 010: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 005 Device 007: ID 24f0:2037 Metadot DK4Q
Bus 005 Device 005: ID 0424:2744 Microchip Technology, Inc. (formerly SMSC) Hub
Bus 005 Device 003: ID 0bda:5413 Realtek Semiconductor Corp. Dell dock
Bus 005 Device 002: ID 0bda:5487 Realtek Semiconductor Corp. Dell dock
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[afranco@localhost-live Code]$ 
[afranco@localhost-live Code]$



And for good measure, output of journalctl -u fprintd.service -p4:

[afranco@localhost-live Code]$ journalctl -u fprintd.service -p4
Dec 27 22:01:04 localhost-live fprintd[1721]: Failed to garbage collect duplicate print, cannot continue with enroll: Passed (print) data is not valid.
-- Boot d308400fa2f74c4a9d507f9455b6f862 --
Dec 27 22:13:25 localhost-live fprintd[1490]: Failed to garbage collect duplicate print, cannot continue with enroll: Passed (print) data is not valid.
Dec 27 22:15:54 localhost-live fprintd[3875]: Failed to garbage collect duplicate print, cannot continue with enroll: Passed (print) data is not valid.
Dec 27 22:25:30 localhost-live fprintd[5233]: Failed to garbage collect duplicate print, cannot continue with enroll: Passed (print) data is not valid.
[afranco@localhost-live Code]$ 
[afranco@localhost-live Code]$




I’ve read a few other posts on the forum about fingerprint issues on Fedora 37, but I don’t believe I’ve found a post with this error message yet. Any advice and guidance would be greatly appreciated

2

Fedora 37 should work out of the box, zero extra config. Was this an upgrade from 36?

The service is running, so that’s a start.

Odd question, but are you powering your Framework through a third party hub or third party AC adapter (looking at your logs)? I’ve seen udev_hotplug_event like this when users are not using the provided power adapter.

Looking at lsusb indicates your reader is detected.

Please try the following:

  • Lose the dock(s) for while we get this working, just on a hunch.
  • Run
dnf list installed | grep fprint

to make sure libfprint, frpintd, and frpintd-pam are installed.
If they are not, install them.

  • Run
sudo systemctl restart fprintd
  • Run
fprintd-delete $USER

to make sure all the old prints are gone.

  • Now re-enroll your fingerprint(s).

If none of this works, I’d try a clean installation - Fedora 37 does support fingerprint usage.

3

@Alex_Franco - you might try clearing the prints using the appimage from this post: [SOLVED] Fingerprint scanner compatibility with linux (ubuntu, fedora, etc) - #214 by Devyn_Cairns

I had used the python script successfully in the past, but I did have issues with it one time, and the appimage worked. It may be worth a try before reinstalling. I suspect that you have enrolled prints left over from your windows installation. Good luck!

1 Like
4

This very well could be.

1 Like
5

@lbkNhubert, this solved the problem! I was hoping the Python script would’ve done this, but looks like the appimage took care of them.

Thank you both very much for the help, appreciate it!

1 Like
6

Glad that it worked, hopefully you can use and enjoy the machine now rather than troubleshooting the fingerprint reader.

1 Like
7

Going forward, I’ve also revamped the fingerprint section of the Fedora 37 guide (right side of section 5).

Configure fingerprint reader
Install the needed packages
sudo dnf install fprintd fprintd-pam

Make sure the service is enabled and running

systemclt status fprintd.service

If it needs to be enabled or started

systemclt enable fprintd.service
systemclt start fprintd.service

Erase any old prints
fprintd-delete $USER

Let’s enroll your new fingerprints
fprintd-enroll

Verify new fingerprints
fprintd-verify

Make sure PAM is authenticated for fingerprints

sudo authselect enable-feature with-fingerprint
sudo authselect apply-changes

Verify it

sudo authselect current

Upon reboot, your fingerprint will allow you login.

1 Like
8

Hey, when trying to add fingerprints in the users tab in gnome settings in fedora, im prompted with the following error:

Failed to claim fingerprint device Goodix MOC Fingerprint
Sensor: failed to communicate with the fingerprint reader

I am using a 13th Gen Intel Framework 13, that I just bought new. I tried to follow the setup guides as accurately as possible.
I couldn’t find any existing posts about this issue. Any help would be much appreciated!

1 Like
9

Hi and welcome to the forum.

Please search: For example

10

Details here as to what is happening and what we’re doing about it on 13th gen.