FS#65258 - [fprintd] AuthenTec AES2501 doesn't work

Attached to Project: Arch Linux
Opened by Viktor Merzlyakov (1024) - Friday, 24 January 2020, 19:27 GMT
Last edited by Toolybird (Toolybird) - Friday, 22 September 2023, 07:00 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan Alexander Steffens (heftig)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Fprintd doesn't work with AuthenTec AES2501. Fresh install Arch Linux (5.4.12-arch1-1), installing fprintd 0.9.0-1, I'm getting device able to recognize, fingerprint-gui and all other tools showing the device correctly, but fprintd-enroll just does nothing after showing "Enrolling %finger% finger" message, as well as fingerprint-gui, though I do enroll my finger. Fprint-demo after manual building shows "error loading enrolled prints" message and doesn't allow to enroll something. I added my user to plugdev group and ensured that all .fp* folders in ~/ have proper rights and ownership. Also I created an udev rule as was suggested here: https://unix.stackexchange.com/questions/365409/fingerprint-gui-only-working-as-root and it allowed me to run fingerprint-gui and fprint-demo as non-root user, but nothing more.
Nothing of I found in the Internet doesn't work. In Windows 7 on this machine (HP Compaq 8710w) sensor works fine.


Additional info:
* package version(s)
fprintd 0.0.0-1
* config and/or log files etc.
lsusb:
Bus 005 Device 002: ID 08ff:2580 AuthenTec, Inc. AES2501 Fingerprint Sensor
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 255 Vendor Specific Subclass
bDeviceProtocol 255 Vendor Specific Protocol
bMaxPacketSize0 8
idVendor 0x08ff AuthenTec, Inc.
idProduct 0x2580 AES2501 Fingerprint Sensor
bcdDevice 6.23
iManufacturer 0
iProduct 1 Fingerprint Sensor
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0020
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0020 1x 32 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 0
can't get debug descriptor: Resource temporarily unavailable
Device Status: 0x0000
(Bus Powered)

# systemctl status fprintd
● fprintd.service - Fingerprint Authentication Daemon
Loaded: loaded (/usr/lib/systemd/system/fprintd.service; static; vendor preset: disabled)
Active: inactive (dead)
Docs: man:fprintd(1)

(after starting the service manually, it becomes:
● fprintd.service - Fingerprint Authentication Daemon
Loaded: loaded (/usr/lib/systemd/system/fprintd.service; static; vendor preset: disabled)
Active: active (running) since Sat 2020-01-25 01:21:29 MSK; 1s ago
Docs: man:fprintd(1)
Main PID: 81045 (fprintd)
Tasks: 4 (limit: 2369)
Memory: 1.4M
CGroup: /system.slice/fprintd.service
└─81045 /usr/lib/fprintd

but no changes at commands behavior)

strace fprintd-enroll log is attached as file.

* link to upstream bug report, if any

Steps to reproduce:
fprintd-enroll
This task depends upon

Closed by  Toolybird (Toolybird)
Friday, 22 September 2023, 07:00 GMT
Reason for closing:  Upstream
Additional comments about closing:  Does not appear to be an Arch packaging issue. If still happening with latest pkgs, please report upstream. Please also refer to the Arch wiki:
https://wiki.archlinux.org/title/Fprint
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...