Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#71431 - [fprintd] Enroll result: enroll-disconnected

Attached to Project: Arch Linux
Opened by Heinrich Heinzer (hheinzer) - Sunday, 04 July 2021, 08:56 GMT
Last edited by Toolybird (Toolybird) - Monday, 25 September 2023, 04:03 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan Alexander Steffens (heftig)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 7
Private No

Details

Description:

Since the last update fprintd stopped working on my ThinkPad X1 Nano.
The message shown is:
```
[hhh@X1Nano ~]% fprintd-enroll hhh
Using device /net/reactivated/Fprint/Device/0
Enrolling right-index-finger finger.
Enroll result: enroll-disconnected
```

This is shown for `journalctl -u fprintd.service`:
```
Jul 04 10:49:52 X1Nano systemd[1]: Starting Fingerprint Authentication Daemon...
Jul 04 10:49:52 X1Nano systemd[1]: Started Fingerprint Authentication Daemon.
Jul 04 10:49:59 X1Nano fprintd[2752]: Device asked for more prints than we are providing.
Jul 04 10:49:59 X1Nano fprintd[2752]: Device reported an error during identify for enroll: Unexpected index
```

I did try the vanilla Linux kernel, as well as the LTS kernel, the result is the same on both.

The bug is especially annoying because when I log in, `gdm` tries to use the fingerprint reader, but fails. Each fail causes an incorrect password attempt and after three the login is locked for 3+ minutes.


Additional info:
* fprintd 1.92.0-1
* ThinkPad X1 Nano
* Linux X1Nano 5.12.14-zen1-1-zen #1 ZEN SMP PREEMPT Thu, 01 Jul 2021 03:35:38 +0000 x86_64 GNU/Linux

Steps to reproduce:

1. Install `fprint` group
2. `fprintd-enroll <username>`
This task depends upon

Closed by  Toolybird (Toolybird)
Monday, 25 September 2023, 04:03 GMT
Reason for closing:  Upstream
Additional comments about closing:  Old and stale. Does not appear to be an Arch packaging issue. If still happening with latest pkgs, please report upstream.
Comment by Shelby Medina (Shelbster) - Sunday, 04 July 2021, 16:14 GMT
This issue also exists on ThinkPad X1 Carbon Gen 9 on 5.12.14-arch1-1. This is after two fresh installs and still no dice.

The issue was not present back in May when I freshly install Arch on a different X1 Carbon Gen 9.
Comment by Nico Wellpott (mightyBroccoli) - Sunday, 04 July 2021, 22:09 GMT
The issue also happens on the T14 AMD Gen1.

Kernel: Linux mahogany 5.12.14-arch1-1 #1 SMP PREEMPT Thu, 01 Jul 2021 07:26:06 +0000 x86_64 GNU/Linux
fprintd & libfprint: 1.92.0-1

journald log lines after `fprintd-verify`
Jul 04 23:37:46 mahogany fprintd[21497]: Device reported an error during identify: Print was not found on the devices storage.
Jul 04 23:38:05 mahogany fprintd[21497]: Device reported an error during verify: Print was not found on the devices storage.

I removed my fingerprint with `fprintd-delete` to see if readding the fingerprint would fix the issue resulting in the fprintd daemon responding with the log lines from the original issue.
Jul 04 23:39:29 mahogany fprintd[21666]: Device asked for more prints than we are providing.
Jul 04 23:39:29 mahogany fprintd[21666]: Device reported an error during identify for enroll: Unexpected index
Comment by David V (davidovitch) - Tuesday, 06 July 2021, 11:31 GMT
Seems to be an issue with fprintd 1.92.0-1 since downgrading to 1.90.9-1 solves if for me. It manifested itself by not showing any users in gdm, and it took me a while before I figured out fprintd was the culprit. I did not see any other hints in the journald log (for example as reported above) of what was going on.

Jul 06 08:34:37 fprintd[2258]: /usr/lib/fprintd: symbol lookup error: /usr/lib/fprintd: undefined symbol: fp_device_has_feature, version LIBFPRINT_2.0.0
Jul 06 08:34:37 systemd[1]: fprintd.service: Main process exited, code=exited, status=127/n/a
Jul 06 08:34:37 systemd[1]: fprintd.service: Failed with result 'exit-code'.
Jul 06 08:34:37 systemd[1]: Failed to start Fingerprint Authentication Daemon.
Comment by Heinrich Heinzer (hheinzer) - Wednesday, 07 July 2021, 06:27 GMT
Yes I can confirm that downgrading to 1.90.0-1 fixes the issue
Comment by Armel Larcier (armellarcier) - Monday, 19 July 2021, 20:40 GMT
I'm getting the same errors. I just installed fprintd so I can't downgrade (easily)

juil. 19 22:39:00 armel-x1 fprintd[9639]: Device asked for more prints than we are providing.
juil. 19 22:39:00 armel-x1 fprintd[9639]: Device reported an error during identify for enroll: Unexpected index
Comment by Iyan (iyanmv) - Tuesday, 20 July 2021, 08:41 GMT
Yes, you can. You can use the archive.

sudo pacman -U https://archive.archlinux.org/packages/f/fprintd/fprintd-1.90.9-1-x86_64.pkg.tar.zst

Later you can add fprintd to the IgnorePkg list in /etc/pacman.conf to avoid updating it automatically when you do a pacman -Syu. Keep an eye to this open bug, and when it gets fixed you can remove it and update.
Comment by everytrash (everytrash) - Wednesday, 21 July 2021, 07:25 GMT
I have also this problem.

- ThinkPad X1 Carbon Gen 8
- Bus 001 Device 006: ID 06cb:00bd Synaptics, Inc. Prometheus MIS Touch Fingerprint Reader

Downgrade works!
Comment by Caleb Cushing (xenoterracide) - Friday, 06 August 2021, 00:01 GMT
There's an upstream bug for this libfrint 1.92.1 (or 2?) should work. you can build the ABS PKGBUILD, replace the commit with master and that works for this error. I personally have just downgraded for this version though.
Comment by Caleb Cushing (xenoterracide) - Friday, 06 August 2021, 00:02 GMT
Here's a link to *my* upstream bug on this issue, which links to the other issue/patch https://gitlab.freedesktop.org/libfprint/fprintd/-/issues/112#note_1016191
Comment by Buggy McBugFace (bugbot) - Tuesday, 08 August 2023, 19:11 GMT
This is an automated comment as this bug is open for more then 2 years. Please reply if you still experience this bug otherwise this issue will be closed after 1 month.

Loading...