Hi, Please be careful with fprintd-pam update. It might happen that you might not be able to log in to your computer anymore as it happened to me. The story is approximately as follows: 1) You install your computer. 2) You install SSSD, configure it and live happy ever after. 3) But there is some new functionality and new default in authconfig introduced [1], but the computer keeps working, because the configuration is not applied. 4) Then there is discovered, that if fprintd-pam is removed, there is some harmless error reported in logs and there is fix applied [2]. 5) As it turns out, the fingerprint reader is actually unregistered by every update, since there is bug in the scriptlet [3]. This is fixed but it triggers the update and PAM configuration update. 6) Since the PAM configuration was updated, the new default from (3) is applied and therefore I cannot login anymore. I believe, that the "authconfig --update" should not be called automatically during update and no other package does that as far as I can tell. Therefore, I reported this into BZ [4], but since I am not PAM expert, any comments are welcome. Vít [1] https://bugzilla.redhat.com/show_bug.cgi?id=1195817 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1203671 [3] https://bugzilla.redhat.com/show_bug.cgi?id=1398371 [4] https://bugzilla.redhat.com/show_bug.cgi?id=1423480 _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
