Comment # 7 on bug 1207788 from
(In reply to Martin Wilck from comment #5)
> (In reply to Alynx Zhou from comment #1)
> > Hi, I see you are using Leap, could you please try to install another
> > tumbleweed and see whether this still happens? We don't have a correct PAM
> > config for fingerprint login until recently I added one to tumbleweed. If
> > tumbleweed works for you, I could also add it to Leap.
> 
> That's not so easy, as this is my primary workstation. At least it will take
> time. Would it be possible to just pull in some fixed package(s) on Leap?
> 

Then please try my other comments about manually edit `gdm-fingerprint` pam
file.

> > Also, is this only happens recently, or always on this device? I think gdm
> > fingerprint login never works on Leap.
> 
> As I said, this is a new phenomenon. gdm fingerprint did work for me, on
> both Leap 15.3 and 15.4, on this system. I basically just installed and
> enabled fprintd, enrolled my fingerprint, and ran "pam-config -a --fprintd".
> 

I see, that because we don't have a PAM config with fprintd, so you have to
manually add it.

> The fingerprint detection itself is much less reliable as I am used to e.g.
> from Android devices, but it's not unusable. I did observe some strange
> effects in the past:
> 
>  1. The fact that the password prompt is displayed makes you think that you
> could use either method for logging in, but it seems that (sometimes at
> least) password login only becomes possible after a certain number (3?) of
> fprint detection failures

Actually GDM supports run different PAM config in parallel, but because we
don't have a proper config for fingerprint, they disabled this feature. I've
added config and enabled the feature, but only in Tumbleweed currently.

>  2. sometimes, if fingerprint detection fails a few times in a row, the
> display gets slightly garbled, but it's normally possible to log in with
> password
> 
> These were annoying, but by far not as destructive as the bug reported here.

I'll try to branch and make a Leap package now.


You are receiving this mail because: