You are not logged in.

#1 2022-06-26 16:35:27

logothete
Member
Registered: 2022-01-06
Posts: 44

Fprintd-enroll throws "unknown error" even though enroll stage passes

I have an HP Envy ep1020. My fingerprint reader, sadly, isn't supported in standard libfprint. Lucky for me, it is supported in libfprint-elanmoc2-git.

lsusb | grep Elan
Bus 003 Device 004: ID 04f3:0c4c Elan Microelectronics Corp. ELAN:ARM-M4

Here's what's installed:

pacman -Qs fprint
local/fprintd 1.94.2-1 (fprint)
    D-Bus service to access fingerprint readers
local/libfprint-elanmoc2-git 1.94.0+10+gd348f17-1 (fprint)
    Library for fingerprint readers with patches for the support of the ELAN 0C4C.
local/pam-fprint-grosshack 0.2.0-1
    PAM module enabling simultaneous fingerprint (fprintd) and password authentication

When I enroll my fingerprint, it actually seems to work, prior to failure:

fprintd-enroll               
Using device /net/reactivated/Fprint/Device/0
Enrolling right-index-finger finger.
Enroll result: enroll-stage-passed
Enroll result: enroll-unknown-error

Trying to look in the journal to get an understanding of what happens:

journalctl -u fprintd.service
...
Jun 26 11:50:42 psyche systemd[1]: Starting Fingerprint Authentication Daemon...
Jun 26 11:50:42 psyche systemd[1]: Started Fingerprint Authentication Daemon.
Jun 26 11:50:43 psyche fprintd[87406]: libusb: error [udev_hotplug_event] ignoring udev action change
Jun 26 11:50:43 psyche fprintd[87406]: libusb: error [udev_hotplug_event] ignoring udev action change
Jun 26 11:50:51 psyche fprintd[87406]: Device reported an error during enroll: transfer timed out

So, the transfer times out, and libusb isn't happy with me. Searching for that libusb error only seems to get me to results for action "bind" instead of change.

Any ideas would be very much appreciated!

Offline

#2 2023-05-10 12:58:33

topongo
Member
Registered: 2019-10-30
Posts: 17

Re: Fprintd-enroll throws "unknown error" even though enroll stage passes

Hi, I have the same issue, have you found a solution in the meantime? The only difference is that the first stages pass, then fprintd-enroll continue to ask me to remove the finger and retry:

$ sudo fprintd-enroll
Using device /net/reactivated/Fprint/Device/0
Enrolling right-index-finger finger.
Enroll result: enroll-stage-passed
Enroll result: enroll-stage-passed
Enroll result: enroll-stage-passed
Enroll result: enroll-stage-passed
Enroll result: enroll-stage-passed
Enroll result: enroll-stage-passed
Enroll result: enroll-stage-passed
Enroll result: enroll-stage-passed
Enroll result: enroll-remove-and-retry
Enroll result: enroll-remove-and-retry
Enroll result: enroll-remove-and-retry
Enroll result: enroll-unknown-error

While fprintd.service produces this output:

May 10 14:57:09 PathFinder systemd[1]: Starting Fingerprint Authentication Daemon...
May 10 14:57:09 PathFinder systemd[1]: Started Fingerprint Authentication Daemon.
May 10 14:57:10 PathFinder fprintd[39877]: libusb: error [udev_hotplug_event] ignoring udev action change
May 10 14:57:10 PathFinder fprintd[39877]: libusb: error [udev_hotplug_event] ignoring udev action change
May 10 14:57:26 PathFinder fprintd[39877]: Device reported an error during enroll: transfer timed out

Thank you in advance.

Offline

#3 2023-05-10 13:19:54

logothete
Member
Registered: 2022-01-06
Posts: 44

Re: Fprintd-enroll throws "unknown error" even though enroll stage passes

Sadly, I never found a solution and I don't even have that laptop anymore! the damnable thing caught on fire!

Offline

#4 2024-01-22 22:00:08

tasman
Member
Registered: 2024-01-22
Posts: 1

Re: Fprintd-enroll throws "unknown error" even though enroll stage passes

SOLVED:  (At least on my HP laptop.)

The problem is that fingerprints are actually stored in the fingerprint reader.  If they've been registered in Windows they must be cleared before registering in Linux or an unknown error is generated.  Once deleted from Windows Hello, fprintd registration works fine in Linux.

Offline

Board footer

Powered by FluxBB