After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 410853 - gnome-screensaver does not support fingerprint authentication through PAM
gnome-screensaver does not support fingerprint authentication through PAM
Status: RESOLVED DUPLICATE of bug 411293
Product: gnome-screensaver
Classification: Deprecated
Component: general
2.16.x
Other All
: Normal minor
: ---
Assigned To: gnome-screensaver maintainers
gnome-screensaver maintainers
Depends on:
Blocks:
 
 
Reported: 2007-02-22 15:46 UTC by Gintautas Miliauskas
Modified: 2007-02-23 18:19 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Gintautas Miliauskas 2007-02-22 15:46:49 UTC
Please describe the problem:
gnome-screensaver claims that it supports PAM authentication, but it appears that PAM support is incomplete, because I cannot use the fingerprint scanner on my laptop (which works through a PAM module) to authenticate.  Authentication by fingerprints works for GDM, sudo, su, login and most other PAM applications.

Steps to reproduce:
1. Lock screen.
2. Try to unlock screen.


Actual results:
The password dialog does not indicate an option to swipe a finger instead of entering a password, nor does swiping a finger work.

Expected results:
Swiping a finger should unlock the screen.

Does this happen every time?
Yes.

Other information:
The problem was reported on the thinkfinger mailinglist (thinkfinger is the fingerprint software and PAM module) here: 
http://article.gmane.org/gmane.linux.drivers.thinkfinger/92

The message seems to indicate that someone is working on this, but I thought this should be recorded on the issue tracker to make sure that it does not get lost.
Comment 1 William Jon McCann 2007-02-23 18:19:44 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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