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/
Forwarded Message
Subject:fprintd-verify
Date: Mon, 25 Mar 2024 15:58:25 +0100
From:
edge and deep statistics/
Forwarded Message ----
Subject:fprintd-verify
Date: Mon, 25 Mar 2024 15:58:25 +0100
From: Eric J.P.E. Davanture
Organization: ⚡ [헗헔헩]⚠
To: fprint@lists.freedesktop.org
Greetings,
On SLED 15 SP5 running on HP ZBook 17 G8 Fury with integrated
finger
Greetings,
On SLED 15 SP5 running on HP ZBook 17 G8 Fury with integrated
fingerprint sensor, fprint now works fine to unlock (KDE Plasma X11)
desktop. Great feature ! Thanks a lot !!
Problem is that fprintd-verify from a command prompt always return a "no
match" when I am sure
Thanks for the tip. It did solve it :).
On Sat, Apr 27, 2013 at 10:23 PM, Tom Chiverton
tom+fpr...@falkensweb.comwrote:
On Friday 26 April 2013 22:43:30 Oz Tamari wrote:
My setup is: Gentoo, libfprint-0.5.0, fprintd-0.4.1
That was me :-)
All I can say is I made sure to enrol as large
On Friday 26 April 2013 22:43:30 Oz Tamari wrote:
My setup is: Gentoo, libfprint-0.5.0, fprintd-0.4.1
That was me :-)
All I can say is I made sure to enrol as large (covering the whole top to
bottom) of my finger(s) as I could.
This made verifying mcuh more reliable; about 70% of the time
.
Enroll result: enroll-completed
ozt@plan9 ~ $ fprintd-verify -f 7
Using device /net/reactivated/Fprint/Device/0
Listing enrolled fingers:
- #0: right-index-finger
Verify result: verify-no-match (done)
ozt@plan9 ~ $ lsusb
Bus 004 Device 002: ID 08ff:2810 AuthenTec, Inc. AES2810
/var/log/messages
