On Fri, 2021-03-05 at 17:20 +0000, Tom Seewald wrote: > > Can you please provide output of `authselect current`? > # authselect current > Profile ID: sssd > Enabled features: > - with-fingerprint > - with-silent-lastlog > > # authselect check > Current configuration is valid. > > I have verified that both sssd and fprintd are running, and are not > logging any errors. Hmm, that might be a different issue then. I don't have a good idea right now, GDM complaining repeatedly generally means that the fingerprint-auth stack is failing with an error (other than PAM_AUTHINFO_UNAVAIL) Could you modify fprintd.service, to set G_MESSAGES_DEBUG=all[1] and then grab a log of that? This will also tell us what is going on in pam_fprintd, and maybe from there we understand why the fingerprint-auth stack seems to be throwing errors. Benjamin [1] You can use systemd edit fprintd.service, then write: [Service] Environment=G_MESSAGES_DEBUG=all and safe that.
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
