Bug#1021045: gdm3: gdm-fingerprint fails if fprintd is installed but libpam-fprint is not

[Ross Vandegrift]

Control: reassign -1 fprintd

Hello,

On Sun, Nov 13, 2022 at 03:00:26PM +0000, Simon McVittie wrote:
> On Fri, 30 Sep 2022 at 21:37:20 -0700, Ross Vandegrift wrote:
> > If fprintd and gdm3 are installed, but libpam-fprintd is not installed, then
> > users with enrolled fingerprints cannot login.
> ...
> > Installing libpam-fprintd fixes the issue.  Perhaps it should be in Recommends
> > instead of Suggests?
> 
> I'm not sure about this as a solution. I don't think it would be true
> to say that installations of gdm3 that don't need (libpam-)fprintd
> are unusual, which is the level of dependency where Recommends are
> necessary. Most gdm3 users log in with a password and don't use a
> fingerprint reader.

Yea, fair enough.  I've posted an issue to gdm upstream gitlab with a request
for better UX in this case.

FingerForce team - Would you consider adding libpam-fprintd to fprintd's
Recommends?  After installing fprintd and enrolling a fingerprint, I couldn't
login with gdm even though the option was presented.

Strictly, it might be excessive (enlightenment could use fprintd without
libpam-fprintd for unlock).  But there's an awkward usability issue now since
nothing pulls it in automatically.

If not, I can add it to enlightenment (along with fprintd).  But it seems
non-optimal to require this on every WM/desktop env package.


Thanks,
Ross