Bug 236070 - gnome-screensaver doesn't work with thinkfinger
gnome-screensaver doesn't work with thinkfinger
Product: Fedora
Classification: Fedora
Component: gnome-screensaver (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Ray Strode [halfline]
Depends On:
  Show dependency treegraph
Reported: 2007-04-11 15:40 EDT by Bryan O'Sullivan
Modified: 2007-11-30 17:12 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-04-11 17:52:59 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
GNOME Desktop 411293 None None None Never

  None (edit)
Description Bryan O'Sullivan 2007-04-11 15:40:47 EDT
Description of problem:

I'm using thinkfinger from Extras, and while almost everything (sudo, login,
gdm, etc) is happy to accept a fingerprint swipe instead of a password,
gnome-screensaver insists on just a password.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Install thinkfinger.
2. Edit /etc/pam.d/system-auth to add a thinkfinger line as the second entry
   in the auth block:
   auth sufficient pam_thinkfinger.so
Actual results:

Everything I've tried except for gnome-screensaver accepts a finger swipe.
Comment 1 Bryan O'Sullivan 2007-04-11 15:41:42 EDT
I'm filing this against gnome-screensaver because googling suggests that
gnome-screensaver is at fault, not thinkfinger.
Comment 2 Ray Strode [halfline] 2007-04-11 17:52:59 EDT
Actually it is thinkfinger's bug.  PAM modules shouldn't expect to be run with
root privileges.  Jon (the author of gnome-screensaver) wrote some patches to
make thinkfinger work better, though. Have a look at:


There is an upstream gnome report here with more information here:

Anyway, closing since it's a thinkfinger problem that should get fixed upstream.

Note You need to log in before you can comment on or make changes to this bug.