Bug 675377 - Fingerprint based authentication hangs when coming from screen-lock / stand by
Summary: Fingerprint based authentication hangs when coming from screen-lock / stand by
Status: RESOLVED FIXED
Alias: None
Product: openSUSE 11.4
Classification: openSUSE
Component: GNOME (show other bugs)
Version: RC 2
Hardware: x86-64 SUSE Other
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords: security
Depends on:
Blocks:
 
Reported: 2011-02-26 08:57 UTC by Eduard Korenschi
Modified: 2013-11-23 20:02 UTC (History)
3 users (show)

See Also:
Found By: Beta-Customer
Services Priority:
Business Priority:
Blocker: No
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eduard Korenschi 2011-02-26 08:57:16 UTC
I have a Dell Latitude D630 with a finger print reader. I activated it in Yast->Hardware and in User management. It works ok when logging in after reboot, but if the screen got locked (by me or after 15 mins), then it will only ask for password (not the fingerprint) and after inputting the right password it hangs indefinitely validating something.

The workaround for me was to go to a screen console and 'kill -9' the process "/usr/bin/X :0 -br -verbose -auth /var/run/gdm/auth-for-gdm-xxxxx/database -nolisten -tcp vtx".

After disabling the fingerprint reader (in yast->hardware) everything went back to normal.
Comment 1 Vincent Untz 2011-02-26 18:49:05 UTC
Fred, just wondering if you have any idea about that? (since you played with fingerprint readers)
Comment 2 Frederic Crozat 2011-02-28 09:14:50 UTC
it would be better to check in /var/log/auth.log

the way we handle fingerprint (pam_fp) is known to be racy, IIRC, we should try to switch to fprintd (but it won't be in 11.4).
Comment 3 Casual J. Programmer 2011-03-16 11:19:50 UTC
Same happens here with a Compaq 8510p and AuthenTec AES2501
yast2-fingerprint-reader-2.20.0-1.6.x86_64
openSUSE 11.5 M0
Comment 4 Dominique Leuenberger 2013-11-23 20:02:01 UTC
Dear Reporter,

Thank you for taking the time to report this bug and helping to make openSUSE better.

We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in openSUSE since the time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a current, supported openSUSE version.

When you test it and it is still an issue, kindly reopen this bug and move it to the tested version of openSUSE. 

Truly yours.