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 429830 - screensaver can not use thinkfinger.
screensaver can not use thinkfinger.
Status: RESOLVED DUPLICATE of bug 411293
Product: gnome-screensaver
Classification: Deprecated
Component: dialog
2.18.x
Other All
: Normal normal
: ---
Assigned To: gnome-screensaver maintainers
gnome-screensaver maintainers
Depends on:
Blocks:
 
 
Reported: 2007-04-15 00:24 UTC by Peng Huang
Modified: 2007-04-23 15:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Peng Huang 2007-04-15 00:24:04 UTC
Please describe the problem:
screensaver can not use thinkfinger.

Steps to reproduce:
1. Install tinkfinger for T41 or some other Laptops with finger scanner.
2. Edit /etc/pam.d/system-auth, add new line before pam_unix.so (It's for Fedora system, other system maybe need modify other file.)
auth        required      pam_env.so
+ auth        sufficient    pam_thinkfinger.so
auth        sufficient    pam_unix.so nullok try_first_pass
3. /usr/sbin/tf-tool --add-user username
3.1 swipe your finger three times to let tf-tool get you fingerprint.
4. start screensaver, and goto the unlock-dialog.
5. you can only use password to unlock screen, you can not use fingerprint to unlock the screen.


Actual results:
Like login, su, sudo, gdm, they will show a prompt test "password or wipe finger", and user can use fingerprint to login system.

Expected results:
you can only use password to unlock screen, you can not use fingerprint to unlock the screen.

Does this happen every time?
yes.

Other information:
Comment 1 William Jon McCann 2007-04-23 15:40: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 ***