Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 2021-03-05 at 18:28 +0000, Tom Seewald wrote:
> > Could you modify fprintd.service, to set G_MESSAGES_DEBUG=all[1]
> > and
> > then grab a log of that?
> 
> Here's what I see from systemctl status fprintd.service:
> 
> Getting authorization to perform Polkit action
> net.reactivated.fprint.device.verify
> Authorization granted to AuthenTec AES2550/AES2810 to call method
> 'ListEnrolledFingers' for device :1.72!
> file_storage_discover_prints() for user 'tom' in
> '/var/lib/fprint/tom/aes2550/0'
> scan_dev_storedir(): opendir("/var/lib/fprint/tom/aes2550/0") failed:
> Error opening directory “/var/lib/fprint/tom/aes2550/0”: No such file
> or directory
> Requesting device 'AuthenTec AES2550/AES2810' authorization for
> method ListEnrolledFingers from :1.74
> Getting authorization to perform Polkit action
> net.reactivated.fprint.device.setusername
> Getting authorization to perform Polkit action
> net.reactivated.fprint.device.verify
> Authorization granted to AuthenTec AES2550/AES2810 to call method
> 'ListEnrolledFingers' for device :1.74!
> file_storage_discover_prints() for user 'tom' in
> '/var/lib/fprint/tom/aes2550/0'
> scan_dev_storedir(): opendir("/var/lib/fprint/tom/aes2550/0") failed:
> Error opening directory “/var/lib/fprint/tom/aes2550/0”: No such file
> or directory
> 
> It looks like "/var/lib/fprint/" is a completely empty directory on
> my system.

Yeah, that is expected if you have not enrolled any prints.

The log is exactly how I expected it. i.e. pam_fprintd asks whether
there are any prints enrolled for the user. This will return zero
(there are none) and pam_fprintd will return PAM_AUTHINFO_UNAVAIL.

So, from the perspective of PAM, everything seems correct to me. I
think I might need to try and reproduce this myself.

Benjamin

> _______________________________________________
> devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: 
> https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
> Do not reply to spam on the list, report it: 
> https://pagure.io/fedora-infrastructure

Attachment: signature.asc
Description: This is a digitally signed message part

_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux