[Fingerforce-devel] Bug#1147153: fprintd: cannot unlock system (ex when wake up from sleep)

[dan]

Package: fprintd
Version: 1.94.5-4+b1
Severity: important
X-Debbugs-Cc: dcoyme at proton.me

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
I tried to enroll a fingerprint in the kde gui. At first it wasn't reading the
fingerprint at all, so I tried to use the terminal and it worked, but running
sudo command and using the fingerprint to give access would always fail (but
when I would try to $fprintd-verify it would always match), so I found on the
internet that I had to run $ sudo pam-auth update and enable fingerprint from
there. At this point I was able to run sudo and it would allow me to just use
the fingerprint, but I still cannot unlock the system. It asks for the
fingerprint, but when I touch it nothing happens.
   * What was the outcome of this action?
   * What outcome did you expect instead?
I expected it to register the fingerprint from the gui (inside kde settings)
and then for it to work in the terminal and also to be able to unlock the
system.

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: forky/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 7.1.12+deb14-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), LANGUAGE=en_IE:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages fprintd depends on:
ii  dbus                   1.16.2-5+b1
ii  libc6                  2.43-4
ii  libfprint-2-2          1:1.94.10-1
ii  libglib2.0-0t64        2.89.4-2
ii  libpolkit-gobject-1-0  127-3
ii  polkitd                127-3

fprintd recommends no packages.

fprintd suggests no packages.

-- no debconf information