<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 18 December 2014 at 18:57, Garry Williams <span dir="ltr"><<a href="mailto:gtwilliams@gmail.com" target="_blank">gtwilliams@gmail.com</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="">On Thu, Dec 18, 2014 at 10:32 AM, Orion Poplawski <<a href="mailto:orion@cora.nwra.com">orion@cora.nwra.com</a>> wrote:<br>
> On 12/18/2014 08:00 AM, Garry Williams wrote:<br>
</span><span class="">>> kcheckpass[10724]: PAM unable to dlopen(/usr/lib64/security/pam_fprintd.so): /usr/lib64/security/pam_fprintd.so: cannot open shared object file: No such file or directory<br>
>> kcheckpass[10724]: PAM adding faulty module: /usr/lib64/security/pam_fprintd.so<br>
>><br>
>> So there's something that still thinks that this authentication should<br>
>> still be run.<br>
><br>
> Try running:<br>
><br>
> authconfig --update<br>
><br>
> to update the config.<br>
<br>
</span>Well, I did something close to that:<br>
<br>
sudo mv /etc/pam.d/system-auth /tmp<br>
sudo dnf reinstall pam<br>
<br>
That did the trick, too.<br>
<br>
I got there from here: <a href="https://bugzilla.redhat.com/show_bug.cgi?id=505266" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=505266</a><br>
<br>
Perhaps removing fprintd should trigger the call to authconfig(8)?<br>
<span class=""><font color="#888888"><br>
</font></span></blockquote><div>after removing all fprint related rpms I then edit system-auth by adding "-" which tell pam to ignore the missing module.<br><br> -auth sufficient pam_fprintd.so<br><br><br></div><div>...dex<br><br></div></div></div></div>