Hi,
honestly, the PAM stuff is kind of painful, and I don't remember how to
debug it. There is nothing interesting in the log, as far as I can
tell.
I would still expect a PAM misconfiguration of some sort. It should go
into pam_fprintd.so at some point, but e.g. I don't even have that
enabled lo
Greetings Benjamin,
Thanks so much for the quick answer.
Here are my answers to your questions (*==> Like this*):
So, fprintd-verify and fprintd-enroll work, but pam not?
*==> Yes Sir.*
Seems like something is broken in the PAM stack. It is hard to tell what
though, as the only error form fpr
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
>
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."
