The officially official Devuan Forum!

You are not logged in.

#1 2021-10-24 09:28:48

mmaglis
Member
From: Berlin - Germany
Registered: 2018-03-16
Posts: 30  

Chimaera fresh installation: Issues with fingerprint authentication

I need help to configure my laptop to authenticate using the fingerprint device in Devuan 4.0 Chimaera.
The device ID is supported by libfprint and listed in https://fprint.freedesktop.org/supported-devices.html

I have installed packages fprintd, libfprint-2-2, libpam-fprintd from main repository.
I have tried to follow documentation and information found on the internet, but it does not work.

Command 

fprintd-enroll -f right-index-finger <USERNAME>

is stuck for ever on below messages, despite scanning my fingerprint several times.
It is only interrupted by Ctrl+C.

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

Package fprint-demo, used to test the fingerprint device, is no longer available in Devuan 4.0.

What is missing? How can I debug this?

Last edited by mmaglis (2021-10-24 16:26:59)

Offline

#2 2021-10-24 18:52:34

Head_on_a_Stick
Member
From: London
Registered: 2019-03-24
Posts: 1,877  
Website

Re: Chimaera fresh installation: Issues with fingerprint authentication

Does the "freeze" unstick if you wiggle the mouse (or touchpad) repeatedly? It could be waiting for entropy (pointlessly).

If that helps then see http://dev1galaxy.org/viewtopic.php?pid=32269#p32269 for a potential solution.

mmaglis wrote:

How can I debug this?

Check the logs.


antifa ftw!

Offline

#3 2021-10-24 19:40:04

mmaglis
Member
From: Berlin - Germany
Registered: 2018-03-16
Posts: 30  

Re: Chimaera fresh installation: Issues with fingerprint authentication

Head_on_a_Stick wrote:

Does the "freeze" unstick if you wiggle the mouse (or touchpad) repeatedly? It could be waiting for entropy (pointlessly).

If that helps then see http://dev1galaxy.org/viewtopic.php?pid=32269#p32269 for a potential solution.

The above suggested action did not have any effect on my case.

mmaglis wrote:

How can I debug this?

Check the logs.

EDIT: lsusb command shows:

Bus 005 Device 002: ID 08ff:2580 AuthenTec, Inc. AES2501 Fingerprint Sensor

Putting fprintd in debug mode

env G_MESSAGES_DEBUG=all /usr/libexec/fprintd -t

and run until interrupted with Ctrl+C

fprintd-enroll -f right-index-finger <USERNAME>

I get the following debug information:

(fprintd:9225): fprintd-DEBUG: 21:16:53.750: About to load configuration file '/etc/fprintd.conf'
(fprintd:9225): fprintd-DEBUG: 21:16:53.751: Launching FprintObject
(fprintd:9225): libfprint-context-DEBUG: 21:16:53.760: No driver found for USB device 0CF3:9271
(fprintd:9225): libfprint-context-DEBUG: 21:16:53.761: No driver found for USB device 1D6B:0002
(fprintd:9225): libfprint-context-DEBUG: 21:16:53.761: No driver found for USB device 046D:C31C
(fprintd:9225): libfprint-context-DEBUG: 21:16:53.761: No driver found for USB device 0461:4D81
(fprintd:9225): libfprint-context-DEBUG: 21:16:53.761: No driver found for USB device 1D6B:0001
(fprintd:9225): libfprint-context-DEBUG: 21:16:53.761: No driver found for USB device 1D6B:0001
(fprintd:9225): libfprint-context-DEBUG: 21:16:53.761: No driver found for USB device 1D6B:0001
(fprintd:9225): libfprint-context-DEBUG: 21:16:53.761: No driver found for USB device 1D6B:0002
(fprintd:9225): libfprint-context-DEBUG: 21:16:53.761: No driver found for USB device 1D6B:0001
(fprintd:9225): libfprint-context-DEBUG: 21:16:53.761: No driver found for USB device 1D6B:0001
(fprintd:9225): fprintd-DEBUG: 21:16:53.766: entering main loop
(fprintd:9225): fprintd-DEBUG: 21:16:53.767: D-Bus service launched with name: net.reactivated.Fprint

(fprintd:9225): fprintd-DEBUG: 21:18:28.872: Requesting device 'AuthenTec AES2501' authorization for method Claim from :1.289
(fprintd:9225): fprintd-DEBUG: 21:18:28.874: Getting authorization to perform Polkit action net.reactivated.fprint.device.setusername
(fprintd:9225): fprintd-DEBUG: 21:18:28.877: Getting authorization to perform Polkit action net.reactivated.fprint.device.verify
(fprintd:9225): fprintd-DEBUG: 21:18:28.882: Authorization granted to AuthenTec AES2501 to call method 'Claim' for device :1.289!
(fprintd:9225): fprintd-DEBUG: 21:18:28.882: user '<USERNAME>' claiming the device: 0
(fprintd:9225): libfprint-image_device-DEBUG: 21:18:28.979: Image device open completed
(fprintd:9225): libfprint-device-DEBUG: 21:18:28.979: Device reported open completion
(fprintd:9225): libfprint-device-DEBUG: 21:18:28.979: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(fprintd:9225): fprintd-DEBUG: 21:18:28.979: claimed device 0
(fprintd:9225): fprintd-DEBUG: 21:18:28.982: Requesting device 'AuthenTec AES2501' authorization for method EnrollStart from :1.289
(fprintd:9225): fprintd-DEBUG: 21:18:28.982: Getting authorization to perform Polkit action net.reactivated.fprint.device.enroll
(fprintd:9225): fprintd-DEBUG: 21:18:28.989: Authorization granted to AuthenTec AES2501 to call method 'EnrollStart' for device :1.289!
(fprintd:9225): fprintd-DEBUG: 21:18:28.989: start enrollment device 0 finger 7
(fprintd:9225): libfprint-image_device-DEBUG: 21:18:28.989: Activating image device
(fprintd:9225): libfprint-image_device-DEBUG: 21:18:28.989: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
(fprintd:9225): libfprint-SSM-DEBUG: 21:18:28.989: [aes2501] ACTIVATE_NUM_STATES entering state 0
(fprintd:9225): libfprint-aeslib-DEBUG: 21:18:28.989: write 38 regs
(fprintd:9225): libfprint-aeslib-DEBUG: 21:18:28.994: all registers written
(fprintd:9225): libfprint-SSM-DEBUG: 21:18:28.994: [aes2501] ACTIVATE_NUM_STATES entering state 1
(fprintd:9225): libfprint-aes2501-DEBUG: 21:18:28.994: read data 1
.......

/var/log/syslog shows

Oct 24 21:28:16 localhost dbus-daemon[1472]: [system] Activating service name='net.reactivated.Fprint' requested by ':1.291' (uid=0 pid=9300 comm="fprintd-enroll <USERNAME> ") (using servicehelper)
Oct 24 21:28:16 localhost dbus-daemon[1472]: [system] Successfully activated service 'net.reactivated.Fprint'

/var/log/messages shows

Oct 24 21:30:52 localhost kernel: [24125.054482] fprintd[9343]: segfault at 8 ip 00007fe5b949231d sp 00007ffd3f0a9780 error 4 in libfprint-2.so.2.0.0[7fe5b946a000+41000]
Oct 24 21:30:52 localhost kernel: [24125.054501] Code: 56 41 55 49 89 fd 41 54 55 48 89 f5 53 48 83 ec 28 89 54 24 04 64 48 8b 04 25 28 00 00 00 48 89 44 24 18 31 c0 e8 c3 81 fd ff <4c> 8b 75 08 48 8b 5d 00 48 89 44 24 08 4d 85 f6 74 61 31 ed 41 bc

Last edited by mmaglis (2021-10-24 19:47:40)

Offline

#4 2021-10-24 20:04:29

mmaglis
Member
From: Berlin - Germany
Registered: 2018-03-16
Posts: 30  

Re: Chimaera fresh installation: Issues with fingerprint authentication

I found a bug report that looks similar to what I experience.

https://gitlab.freedesktop.org/libfprin … issues/320

Offline

Board footer