# Fingerprint reader fails to recognize enrolled prints on F36 **URL:** \ **Category:** Linux\ **Created:** [May 20, 2022, 4:11am UTC](https://community.frame.work/t/fingerprint-reader-fails-to-recognize-enrolled-prints-on-f36/18739 "2022-05-20T04:11:50Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![SomewhereOutInSpace](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/somewhereoutinspace/32/26525_2.png) [@SomewhereOutInSpace](https://community.frame.work/u/SomewhereOutInSpace)\ **Post date:** [May 20, 2022, 4:11am UTC](https://community.frame.work/t/fingerprint-reader-fails-to-recognize-enrolled-prints-on-f36/18739/1 "2022-05-20T04:11:51Z")
Hey all! I just got my Framework and I’m loving it so far, with the sole exception of weirdness from the fingerprint reader. No matter how many times I delete-and-enroll or which fingers I use, when I try to login or use `fprintd-verify`, it universally fails to recognize my prints. It’s kinda driving me insane; you can see in the screencap below that I actually managed a “perfect” enrollment, yet `fprintd-verify` still insists I’m a stranger. As far as I can tell the reader is functioning fine, it’s just that some nebulous thing has gone wrong between there and Fedora. ![Screenshot from 2022-05-19 23-59-02](https://us1.discourse-cdn.com/flex001/uploads/framework3/original/2X/4/4af76a2a2ec86535e42e64f1e7de6b8086ca2654.png) Any help or pointers would be greatly appreciated! ---
**Author:** ![gjason](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/gjason/32/769_2.png) [@gjason](https://community.frame.work/u/gjason)\ **Post date:** [May 20, 2022, 3:29pm UTC](https://community.frame.work/t/fingerprint-reader-fails-to-recognize-enrolled-prints-on-f36/18739/2 "2022-05-20T15:29:21Z")
I had a similar problem - did you enroll some prints in a different OS, or even a different install of Fedora, then reinstall without removing the enrolled prints in the previous OS install? If so, there’s a [python script here](http://community.frame.work/t/fingerprint-scanner-compatibility-with-linux-ubuntu-fedora-etc/1501/146) that removes any & all prints that are stored in the hardware. ---
**Author:** ![SomewhereOutInSpace](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/somewhereoutinspace/32/26525_2.png) [@SomewhereOutInSpace](https://community.frame.work/u/SomewhereOutInSpace)\ **Post date:** [May 21, 2022, 1:03am UTC](https://community.frame.work/t/fingerprint-reader-fails-to-recognize-enrolled-prints-on-f36/18739/3 "2022-05-21T01:03:12Z")
@gjason - Nope, I went straight for Fedora as soon I finished assembly. (I already use it on my desktop; the out-of-box compatibility with FW just sweetened the deal.) I’ll run the script regardless, just to see. Edit: the script reports zero enrolled prints. I ran it with the `-d` argument anyways, but still no dice. ---
**Author:** ![MDZZ](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/mdzz/32/8565_2.png) [@MDZZ](https://community.frame.work/u/MDZZ)\ **Post date:** [May 23, 2022, 7:34am UTC](https://community.frame.work/t/fingerprint-reader-fails-to-recognize-enrolled-prints-on-f36/18739/4 "2022-05-23T07:34:39Z")
I encountered a similar issue just last week. it worked out-of-box with a fresh Fedora 36 KDE. I enrolled of my fingerprint and it worked as expected. After a few days I tried to add more print(mine and my wife’s). It just won’t recognize any finger after new enroll. I check systemctl status fprintd.service apparently the first verify reports mismatch but what’s weird is right after the failed attempt it decide it does not like my fingerprints and went ahead deleted all of them. I was able to replicate the issue a couple times with just my one fingerprint and a couple prints from me/me and my wife. everytime after fail attempt it deleted all prints. I tried restart/reenable the service and the python script as well. after a couple times of poking around and rebooting it seems fixed itself and I was able to register my print. at this point I decided to leave it be and not adding more prints. ---
**Author:** ![Edward\_Gray](https://avatars.discourse-cdn.com/v4/letter/e/c4cdca/32.png) [@Edward\_Gray](https://community.frame.work/u/Edward_Gray)\ **Post date:** [May 23, 2022, 10:25am UTC](https://community.frame.work/t/fingerprint-reader-fails-to-recognize-enrolled-prints-on-f36/18739/5 "2022-05-23T10:25:12Z")
I had a similar event where I had to re-register my fingerprint after a failed login. I wonder which part of the process caused that. OS was Ubuntu 22.04. ---
**Author:** ![SomewhereOutInSpace](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/somewhereoutinspace/32/26525_2.png) [@SomewhereOutInSpace](https://community.frame.work/u/SomewhereOutInSpace)\ **Post date:** [May 26, 2022, 4:16am UTC](https://community.frame.work/t/fingerprint-reader-fails-to-recognize-enrolled-prints-on-f36/18739/6 "2022-05-26T04:16:14Z")
Unfortunately, it seems I’m still SOL. However, I have noticed another oddity: the reader seems to spontaneously “forget” prints soon after enrolling them, at least some of the time: ![image](https://us1.discourse-cdn.com/flex001/uploads/framework3/original/2X/c/c9ee836620e1204e3c6af91f1ed8c3e231214e51.png) You can see here that I enroll a print, then try to verify it unsuccessfully. However, when I try to run `fprintd-verify` once more, it insists that the reader holds no enrolled prints. This has happened a few times before in my testing; it doesn’t occur consistently, and if it does happen it only seems to rear its head immediately after the reader first tries to poll the newly enrolled print. ---
**Author:** ![MDZZ](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/mdzz/32/8565_2.png) [@MDZZ](https://community.frame.work/u/MDZZ)\ **Post date:** [May 26, 2022, 8:13pm UTC](https://community.frame.work/t/fingerprint-reader-fails-to-recognize-enrolled-prints-on-f36/18739/7 "2022-05-26T20:13:24Z")
Looks like we have similar issue here. Here is my journalctl log. hope it inspires someone to come up with sth. right now I managed to have only my right index finger working. ![Screenshot_20220526_094606](https://us1.discourse-cdn.com/flex001/uploads/framework3/original/2X/7/792a6e61aecdb256cb07a9c5e624cc0bf70f9cf2.png) ---
**Author:** ![SomewhereOutInSpace](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/somewhereoutinspace/32/26525_2.png) [@SomewhereOutInSpace](https://community.frame.work/u/SomewhereOutInSpace)\ **Post date:** [June 27, 2022, 2:51am UTC](https://community.frame.work/t/fingerprint-reader-fails-to-recognize-enrolled-prints-on-f36/18739/8 "2022-06-27T02:51:56Z")
> [@\[TRACKING\] Fingerprint scanner compatibility with linux (ubuntu, fedora, etc)](http://community.frame.work/t/fingerprint-scanner-compatibility-with-linux-ubuntu-fedora-etc/1501/214): > > @CSab6482 I spent some more time on this, and I got together something that should be reasonably easy. I can’t guarantee it will work, and I provide this as-is with zero warranty - it has not been approved by Goodix, the manufacturer of the fingerprint device; I have just taken a guess at how their device works based on some code they left behind. If you wish to verify this, I have signed the checksum file inside there with my GPG signature, FA6FB12588810A870C92609D3901327190847975 Devyn Cai… Heads up: using the program provided in the above post resolved the issue. I still have no fucking clue what the problem was, especially seeing as I never used the reader in Windows, but it’s fixed. @MDZZ @Edward_Gray