fprint on HP ZBook 17 G8 Fury running SuSE Linux Enterprise Desktop 15 SP5

[Benjamin Berg]

Hi,

On Fri, 2024-03-22 at 15:52 +0100, Eric J.P.E. Davanture wrote:
>  
> Greetings,
>  
> I have SuSE Linux Enterprise Desktop (SLED) 15 SP5 and I use KDE
> Plasma X11 with fprintd package installed (v 1.94.2-bp155.2.3.1) to
> unlock the desktop using the integrated fingerprint reader of an HP
> ZBook 17 G8 Fury (lsusb says: "Bus 003 Device 003: ID 06cb:00f0
> Synaptics, Inc." which is supported by fprint). 
>  
> It worked fine for some weeks but after some SLED 15 SP5 updates
> (using zypper up), something broke fprintd package and SuSE Technical
> Support does not find what :-(
>  
> I can't unlock anymore the desktop with my fingerprint. I get
> "Unlocking failed" error message and I have to enter the password
> with the keyboard as before. 
>  
> A few commands I tested:
>  
> └─# journalctl -u fprintd.service 
> Mar 22 11:13:57 HP-ZBook17-G8 systemd[1]: Starting Fingerprint
> Authentication Daemon... 
> Mar 22 11:13:58 HP-ZBook17-G8 systemd[1]: Started Fingerprint
> Authentication Daemon. 
> Mar 22 11:14:57 HP-ZBook17-G8 systemd[1]: fprintd.service:
> Deactivated successfully. 
> Mar 22 15:23:50 HP-ZBook17-G8 systemd[1]: Starting Fingerprint
> Authentication Daemon... 
> Mar 22 15:23:50 HP-ZBook17-G8 systemd[1]: Started Fingerprint
> Authentication Daemon. 
> Mar 22 15:23:53 HP-ZBook17-G8 fprintd[18155]: Authorization denied to
> :1.375 to call method 'Release' for device 'Synaptics Sensors':
> Device was not claimed before use
>  
> └─# fprintd-enroll 
> Using device /net/reactivated/Fprint/Device/0 
> Enrolling right-index-finger finger. 
> Enroll result: enroll-stage-passed 
> Enroll result: enroll-retry-scan 
> Enroll result: enroll-stage-passed 
> Enroll result: enroll-stage-passed 
> Enroll result: enroll-retry-scan 
> 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-retry-scan 
> Enroll result: enroll-completed
> 
> └─# fprintd-verify 
> Using device /net/reactivated/Fprint/Device/0 
> Listing enrolled fingers: 
> - #0: right-index-finger 
> Verify started! 
> Verifying: right-index-finger 
> Verify result: verify-no-match (done)

So, fprintd-verify and fprintd-enroll work, but pam not?

Seems like something is broken in the PAM stack. It is hard to tell
what though, as the only error form fprintd is that Release is called
without first claiming the device, for which I have no explanation.
Maybe auth log has more information?

Also, does it even prompt you for a fingerprint on the console?

Benjamin

> 
>  
> Any idea on how to investigate this problem would be very much
> appreciated.
>  
> Thanks a lot by now.
>  
> 
>  
>  
> Librement vôtre / Libremente suyo / Freely yours,
> Eric J.P.E. Davanture - eric.davanture at orange.fr
> Mobile: +33-607.08.01.78
> Approximate location: Planet Earth < Solar System < Milky Way Galaxy
> < Local Group < Virgo Cluster < Laniakea Supercluster < known
> Universe
> - There are 10 types of people in this world: those who understand
> binary and those who don't
> - There is NO CLOUD, just other people's computers
> - There is NO INTELLIGENCE in AI, just huge knowledge and deep
> statistics
>  
> 
>  
>  

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/fprint/attachments/20240322/ae79116c/attachment.htm>