This appears to be a problem with the hardware stored fingerprints being carried over from one install of ubuntu to another, in some manner where one set of fingerprints obscures a previous set. If I try to enroll a previously un-registered finger, it registered it – sort of. But it didn’t recognize it for login.
Checking out the gitlab bug #415@Bob_U pointed to, I discovered the “Namespace FPrint not available” error was a result of not having gir1.2-fprint-2.0 installed. Installing that allowed the delete script from #415 to run. However, when run, it listed only two fingerprints (I thought I had 3 registered at this point, right-index, right-middle, and right-ring), both right-middle. It deleted the two it seemed to know about, but it did not delete the right-index, as it didn’t seem to know about that one. When run again, it showed no fingerprints.
However, when I went to settings to enroll a new fingerprint, it showed a right-index-fingerprint, and the option to delete. So I clicked delete, and that seemed to work.
Subsequently, I was able to re-enroll my right-index.
Hey all, Im running Kubuntu 21.10 and im following the walkthoughs in this thread but when i get to the build steps it seems ninja isnt quite working. i get the following error ninja: error: loading 'build.ninja': No such file or directory Im not sure where that file would come from what info needs to be included. or if there is an argument on the command im missing? any help would be much appreciated.
@Sam_Lane it looks like you saw a similar error, how did you resolve it?
UPDATE:
I was able to get the ninja build to work by rebooting.
Having an issue with the fingerprint reader in Manjaro XFCE minimal. Big thing is that fingerprint reader is seen by fprintd but not seen by fingerprint-gui. I have tried to use the fprintd setup here: fprint - ArchWiki however it is still not working. Could this be an issue with my greeter (lightdm-slick-greeter as recommended from another thread)?
$ lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 27c6:609c Shenzhen Goodix Technology Co.,Ltd. Goodix USB2.0 MISC
Bus 003 Device 002: ID 0bda:5634 Realtek Semiconductor Corp. Laptop Camera
Bus 003 Device 004: ID 8087:0032 Intel Corp. AX210 Bluetooth
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
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
Edit to add - I get the same initial udev errors, but then it lists my enrolled prints. I didn’t run with -d to delete as things are working ok in my setup and I’d rather not delete the prints.
Has anyone had any luck resolving the udev_hotplug_event error? Mine also follows an error regarding power/persist - here’s the output of fprintd status:
Feb 01 14:20:47 fedora systemd[1]: Starting Fingerprint Authentication Daemon…
Feb 01 14:20:47 fedora fprintd[35044]: Failed to open /sys/bus/usb/devices/3-9/power/persist
Feb 01 14:20:47 fedora fprintd[35044]: libusb: error [udev_hotplug_event] ignoring udev action change
Feb 01 14:20:47 fedora systemd[1]: Started Fingerprint Authentication Daemon.
Feb 01 14:20:47 fedora fprintd[35044]: libusb: error [udev_hotplug_event] ignoring udev action change
Feb 01 14:20:48 fedora fprintd[35044]: libusb: error [udev_hotplug_event] ignoring udev action change
Feb 01 14:20:48 fedora fprintd[35044]: libusb: error [udev_hotplug_event] ignoring udev action change
I just want to note that the fingerprint reader IS WORKING currently on Fedora 35, just curious about these errors…
Do you get the same error when you run the script with the -d flag? Warning, that will delete any enrolled fingerprints if it does work. Have you ever had the fingerprint reader working? I noticed that you are on v1.94 - is there a reason that you need that version? The default one in 21.10 is working fine for me - I understand that you may need it, just asking.
-d did not work, I had old versions of the libs before, but I just tried the newest, I had the fingerprint working on windows before, and pop is 12.04 before that
Have the same parse fingerlist error. I’m pretty sure fingerprint worked once when was using Fedora 34. But now I’m using Manjaro and it doesn’t work. Then I switched back to Fedora, and Fedora also failed
Thank you for your work @Devyn_Cairns. I managed to corrupt storage my goodixmoc even without a dual boot setup, and calling clear_storage_sync while having a version of libfprint with your patch merged in (1.94.3) solved my issue.
Last week, I set up my new Framework using Ubuntu 20.4.4 and everything including the fingerprint scanner was working fine. Then, I decided to install Mint 20.3 and also managed to set up the fingerprint using binaries for libfprint-2-2_1.94.1, fprintd_1.94.0 and libpam-fprintd_1.94.0 which were mentioned earlier in this post here.
Without my intervention, after a day or so, the fingerprint scanner stopped working completely. I reinstalled Ubuntu 20.4.4 but the problem persists. fprint-enroll still gives me
Impossible to enroll: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available
and the fingerprint device does not seem to be recognized anymore since lsusb only reports:
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 32ac:0002 Framework HDMI Expansion Card
Bus 003 Device 009: ID 8087:0032 Intel Corp.
Bus 003 Device 002: ID 046d:c539 Logitech, Inc. USB Receiver
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
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
Do you think think this is a hardware issue? I’ve tried reinserting the fingerprint cable as described in the fingerprint replacement guide but that did not help, unfortunately.
Thanks for pointing that out @Fraoch. I forgot to mention that I successfully used that script to clear the fingerprints from the sensor’s memory after moving from Ubuntu to Mint. However, since the device is now no longer accessible, the script is also not able to accomplish much.
It seems to just skip the loop since there are no fprint_devices returned by print_context.get_devices() which is consistent with lsusb not listening any.
Is there another way I can check whether the device is still functioning? I find it hard to believe that it just stopped working altogether.
still getting no device found/script does not work