On 18 December 2014 at 18:57, Garry Williams <gtwilliams(a)gmail.com> wrote:
On Thu, Dec 18, 2014 at 10:32 AM, Orion Poplawski <orion(a)cora.nwra.com>
wrote:
> On 12/18/2014 08:00 AM, Garry Williams wrote:
>> 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
>> kcheckpass[10724]: PAM adding faulty module:
/usr/lib64/security/pam_fprintd.so
>>
>> So there's something that still thinks that this authentication should
>> still be run.
>
> Try running:
>
> authconfig --update
>
> to update the config.
Well, I did something close to that:
sudo mv /etc/pam.d/system-auth /tmp
sudo dnf reinstall pam
That did the trick, too.
I got there from here:
https://bugzilla.redhat.com/show_bug.cgi?id=505266
Perhaps removing fprintd should trigger the call to authconfig(8)?
after removing all fprint related rpms I then edit system-auth by adding
"-" which tell pam to ignore the missing module.
-auth sufficient pam_fprintd.so
...dex