[TRACKING] Fingerprint scanner compatibility with linux (ubuntu, fedora, etc)

[Philonmetal]

Thanks for looking into this!

As you can see, lsusb gives me in both cases the same output.
So i should consult the support team, because it looks like a hardware fault?

Fedora LiveUSB

6.0.7-301.fc37.x86_64

Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 007: ID 2109:8888 VIA Labs, Inc. USB Billboard Device
Bus 003 Device 008: ID 0424:3fb7 Microchip Technology, Inc. (formerly SMSC) Babyface (23368007)
Bus 003 Device 005: ID 1a40:0801 Terminus Technology Inc. USB 2.0 Hub
Bus 003 Device 010: ID 05ac:0250 Apple, Inc. Aluminium Keyboard (ISO)
Bus 003 Device 009: ID 046d:c332 Logitech, Inc. G502 Proteus Spectrum Optical Mouse
Bus 003 Device 006: ID 046d:c077 Logitech, Inc. Mouse
Bus 003 Device 004: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 003 Device 002: ID 2109:2817 VIA Labs, Inc. USB2.0 Hub
Bus 003 Device 011: ID 8087:0032 Intel Corp. AX210 Bluetooth
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 005: ID 05e3:0749 Genesys Logic, Inc. SD Card Reader and Writer
Bus 002 Device 004: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter
Bus 002 Device 002: ID 2109:0817 VIA Labs, Inc. USB3.0 Hub
Bus 002 Device 003: ID 0781:558c SanDisk Corp. Extreme Portable SSD
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

Fedora Install

6.1.12-200.fc37.x86_64

Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 007: ID 2109:8888 VIA Labs, Inc. USB Billboard Device
Bus 003 Device 008: ID 0424:3fb7 Microchip Technology, Inc. (formerly SMSC) Babyface (23368007)
Bus 003 Device 005: ID 1a40:0801 Terminus Technology Inc. USB 2.0 Hub
Bus 003 Device 010: ID 05ac:0250 Apple, Inc. Aluminium Keyboard (ISO)
Bus 003 Device 009: ID 046d:c332 Logitech, Inc. G502 Proteus Spectrum Optical Mouse
Bus 003 Device 006: ID 046d:c077 Logitech, Inc. Mouse
Bus 003 Device 004: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 003 Device 002: ID 2109:2817 VIA Labs, Inc. USB2.0 Hub
Bus 003 Device 011: ID 8087:0032 Intel Corp. AX210 Bluetooth
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 004: ID 05e3:0749 Genesys Logic, Inc. SD Card Reader and Writer
Bus 002 Device 003: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter
Bus 002 Device 002: ID 2109:0817 VIA Labs, Inc. USB3.0 Hub
Bus 002 Device 005: ID 0781:558c SanDisk Corp. Extreme Portable SSD
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

[Matt_Hartley]

No problem, happy to help. Doesn’t look like we’re seeing Shenzhen Goodix Technology Co.,Ltd. Goodix anywhere. To save you some steps in the upcoming ticket, do the following now and let support know you’ve done this:

• Disconnect everything that is not power from the laptop, re-run the commands in the Live Fedora USB. We both know it won’t matter, but it will be asked. Make a note that Shenzhen Goodix Technology Co.,Ltd. Goodix is still not showing up.

• Open the laptop, double check the connection to the webcam is sound. You can use step 8 in this guide for this. Webcam Replacement Guide - Framework Guides

Then with these things done, open a ticket, link to this post and let support know the Linux lead said this is not a Linux issue and appears to be an issue the camera itself as you’ve checked he connection. They may want photos of the connection.

[Philonmetal]

Thank you, will do that!
Just for reference, its about the Fingerprint Scanner and not the Webcam. I will check the connection to the Fingerprint Reader with this Framework Guide for Fingerprint Reader and make a photo like in step 6.

[Matt_Hartley]

@Philonmetal

Thank you, will do that!

Sounds good.

[Koriko]

Is anyone on NixOS willing to share their configs with me? I’ve tried everything in this thread and had troubleshooting sessions with 2 different people after dedicating two weekends to it and I still am not able to get fprintd working as it should. I keep running into a package crc error every step of the way.

[Matt_Hartley]

@Koriko

Is anyone on NixOS willing to share their configs with me? I’ve tried everything in this thread and had troubleshooting sessions with 2 different people after dedicating two weekends to it and I still am not able to get fprintd working as it should. I keep running into a package crc error every step of the way.

We do have a specific Nix related thread for questions and answers. Might be worth re-posting there as well.

[RESPONDED] NixOS questions

I think there is a (very) small NixOS user community here. Maybe we can coalesce somewhere in this forum for specific NixOS related issues. I have one. Is anyone able to turn the great fw-ectool by DHowett GitHub - DHowett/fw-ectool 2 into a nix package and get it on the Nix “repo”?

[Eliseo_Zamora]

[TRACKING] Fingerprint scanner compatibility with linux (ubuntu, fedora, etc)

I got the fingerprint reader to work to sign in and on sudo. One thing I noticed was after a restart and I use the fingerprint to sign in it doesn’t unlock the keyring. I looked arround and this seems to be intended for security reasons. From what I read it seems your keyring is encrypted using your password and so your fingerprint can’t decrypt it without having your password stored as plain text which is not secure. Did I understand this right? If not anybody know how to get your fingerpr…

Were you able to fix this I recently had the same issue and trying to find a solution to getting the keyring authenticated?

[Matt_Hartley]

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.

[kainisenni]

I installed Fedora 38 yesterday and the fingerprint scanner on my laptop has stopped working, running systemctl status fprintd.service gives me:

Apr 19 14:24:55 framework fprintd[28454]: libusb: error [udev_hotplug_event] ignoring udev action change
Apr 19 14:24:55 framework fprintd[28454]: libusb: error [udev_hotplug_event] ignoring udev action change
Apr 19 14:24:55 framework fprintd[28454]: Template storage appears to have been corrupted! Error was: Corrupted message header>
Apr 19 14:24:55 framework fprintd[28454]: A known reason for this to happen is a firmware bug triggered by another storage are>
Apr 19 14:24:55 framework fprintd[28454]: Resetting device storage, you will need to enroll all prints again!
Apr 19 14:24:55 framework fprintd[28454]: Reset failed: Corrupted message header received
Apr 19 14:25:00 framework fprintd[28454]: libusb: error [udev_hotplug_event] ignoring udev action change
Apr 19 14:25:00 framework fprintd[28454]: libusb: error [udev_hotplug_event] ignoring udev action change
Apr 19 14:25:00 framework fprintd[28454]: libusb: error [udev_hotplug_event] ignoring udev action change
Apr 19 14:25:30 framework systemd[1]: fprintd.service: Deactivated successfully.

fprintd-delete ends with:
failed to claim device: GDBus.Error:net.reactivated.Fprint.Error.Internal: Open failed with error: Corrupted message header received

I have not yet found anyone else with this issue, so is it just a problem with F38 being new or did something go wrong when I upgraded from 37?

[Matt_Hartley]

@kainisenni

I have not yet found anyone else with this issue, so is it just a problem with F38 being new or did something go wrong when I upgraded from 37?

This feels like something didn’t carry over nicely from 37. Also why I always recommend a /home backup and then a clean install with any distro upgrade (unless rolling release). Early upgrades from one release to another vs clean installs tend to open up issues like this.

Please run this program, then reboot, see if the issue still happens. On a clean install, I have zero issues with the fingerprint reader .

[kainisenni]

@Matt_Hartley

This feels like something didn’t carry over nicely from 37. Also why I always recommend a /home backup and then a clean install with any distro upgrade (unless rolling release). Early upgrades from one release to another vs clean installs tend to open up issues like this.

Please run this program, then reboot, see if the issue still happens. On a clean install, I have zero issues with the fingerprint reader .

Thank you, the program did the trick!

[Matt_Hartley]

@kainisenni

Thank you, the program did the trick!

Delighted to hear it!

[MrPeach]

@Devyn_Cairns

If goes well, it should tell you the name of the device and that it cleared it (along with some other libusb and udev related errors you can ignore)

Thank you so much. cannot thank you enough, I was about to give up

[Owen]

I have Mint on my framework and it didn’t work out of the box, but after installing fprintd and libpam-fprintd it worked great.

[Loell_Framework]

Great to hear it works with Linux Mint @Owen

[Marveille_ZINZIN]

Hello everyone! I’m dual-booting Fedora 38 and Windows 11. Have the problem of “corrupted header” so I’ve used the AppImage by @Devyn_Cairns ; I can now register and sign in with fingerprint successfully on Fedora but not any more on Windows: fingerprints are successfully enrolled but not deleted (I can use the remove option in Windows settings but when trying to set up with the same finger, it says “similar fingerprint already set”). Furthermore, signing in with fingerprint not available even when it is set. Thanks in advance for the help.

[Jonathan_Haas]

A specific fingerprint finger can only be assigned to one OS installation. I suggest to clean all stored fingerprints with the given script (from Fedora) and if you really need fingerprints in both Windows and Linux, make sure each OS has its own set of fingers, i.e. if you want to use the real pointer finger for login, store its finger print as the pointer finger in windows and the middle finger in Linux or something like that. (If it complains about a similar finger being already set, you might need to use different fingers for login, i.e. use the pointer finger in windows and the middle finger for linux or something like that)

[Marveille_ZINZIN]

Hello @Jonathan_Haas. Thanks for the answer! I did that, but it didn’t solve the problem: even with a fingerprint added, the login option no longer appears on the Windows login screen; and when I delete that fingerprint and try to set it again, it says that a similar record already exists (no fingerprint set on Fedora).

[Matt_Hartley]

@Marveille_ZINZIN

Thanks for the answer! I did that, but it didn’t solve the problem: even with a fingerprint added, the login option no longer appears on the Windows login screen; and when I delete that fingerprint and try to set it again, it says that a similar record already exists (no fingerprint set on Fedora).

How are you deleting the fingerprint? If you are dual-booting, you might try running this tool (Linux AppImage), then reboot, see if this helps Window at all. The idea being to clear all fingerprint storage completely.

Once this is done in Linux and rebooted back into Windows (if this is where you want to enroll the fingerprint, you will need to re-enroll again.

[Marveille_ZINZIN]

@Matt_Hartley, well, well… I did that, it didn’t work… I thought resetting Windows or reinstalling Fedora would solve the problem (I did both, resetting Windows first and trying to add the fingerprint, but at some point it stopped working). After reinstalling Fedora, it didn’t work anymore (I used the AppImage again) : I now have an unlimited ‘enroll-retry-scan’ after the first scan when using fprintd-enroll. On Windows, Windows Hello kept crashing after the first scan (‘Something went wrong, retry later’; in the event viewer, there’s a Windows Biometrics Service error: ‘failed to delete record from the sensor’).
That’s the situation now! Don’t know if anyone can help me .