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 683131 - Fingerprint authentication configured but never used
Fingerprint authentication configured but never used
Status: RESOLVED FIXED
Product: gnome-shell
Classification: Core
Component: lock-screen
3.5.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2012-08-31 18:01 UTC by Tom 'spot' Callaway
Modified: 2017-03-22 13:27 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
fingerprint: autostart fprintd when necessary (1.84 KB, patch)
2012-09-13 20:07 UTC, Ray Strode [halfline] 		committed Details | Review

Description Tom 'spot' Callaway 2012-08-31 18:01:03 UTC 
Ray helped me debug this, basically, the login/lock screen never prompt to use my configured fingerprint because fprintd wasn't being launched with the right DBUS flags. Or something. I'm hoping this will jog his memory. :)
Comment 1 Ray Strode [halfline] 2012-08-31 18:13:16 UTC 
regression caused by bug 675006
Comment 2 drago01 2012-09-05 09:54:57 UTC 
(In reply to comment #1)
> regression caused by bug 675006

Given that bug 675006 is fixed ... is there anything left here?
Comment 3 Ray Strode [halfline] 2012-09-13 18:50:20 UTC 
yea, my "fix" in bug 675006 actually broke things.  I need to fix it, properly.
Comment 4 Ray Strode [halfline] 2012-09-13 20:07:26 UTC 
Created attachment 224267 [details] [review]
fingerprint: autostart fprintd when necessary

commit e333263fd646cee7b235e181db7dd96a6bf0735e changed fingerprint.js
to not throw an exception when fprintd is uninstalled, by adding the
flags DO_NOT_LOAD_PROPERTIES and DO_NOT_AUTO_START

DO_NOT_LOAD_PROPERTIES is correct.  Loading the properties is what makes
it fail at initialization time when not installed.  DO_NOT_AUTO_START is
not correct though. It means fprintd will never get activated implicitly
when we need it.

This commit removes DO_NOT_AUTO_START thus making fprintd start when we
need it, but not fail at initialization time when not around.
Comment 5 drago01 2012-09-13 20:58:14 UTC 
Review of attachment 224267 [details] [review]:

OK.
Comment 6 Ray Strode [halfline] 2012-09-14 16:13:05 UTC 
Attachment 224267 [details] pushed as 638507c - fingerprint: autostart fprintd when necessary
Comment 7 Ray Strode [halfline] 2017-03-22 13:27:19 UTC 
(In reply to Ray Strode [halfline] from comment #3)
> yea, my "fix" in bug 675006 actually broke things.  I need to fix it,
> properly.

third times a charm? see bug 780063