Bug 1719180

Summary: Login prompt for sudo, su etc takes 30 seconds to appear
Product: [Fedora] Fedora Reporter: Matt Spencer <matthew>
Component: fprintdAssignee: Bastien Nocera <bnocera>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 30CC: bnocera
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-06-11 11:22:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Matt Spencer 2019-06-11 09:09:55 UTC
User-Agent:       Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.169 Safari/537.36
Build Identifier: 

After upgrading packages on a Fedora 30 system around the 30th May, any action that requires a credential check (sudo, su, login screen etc) takes about 30 seconds to appear.

This seems to be a problem with a dbus timeout trying to talk to the fingerprint daemon (more details in the additional details section).

Workaround was to disable fingerprint as a valid login method using authconfig.

Reproducible: Always

Steps to Reproduce:
1.Issue any command that has a password challenge (sudo, su, login etc)
2.
3.
Actual Results:  
Password prompt takes ~30 seconds to appear

Expected Results:  
Password prompt comes up immediately

Upgraded from F29 to F30 and all was find for a while.
About a week ago after an upgrade, i noticed that sudo was taking a long time to get to ask me for a password.  Also it was taking a long time to go from suspend to a login screen.

A quick check with 'strace su -', it looked like the problem was a timeout on a dbus call to an Fprint.xx endpoint.

I am running this on a dell xps13, which I don't believe has a fingerprint reader.

Solution to the problem was to use
  authconfig --disablefingerprint --updateall

and everything is fine again.

Comment 1 Bastien Nocera 2019-06-11 11:22:40 UTC

*** This bug has been marked as a duplicate of bug 1534873 ***