[Bug 448166] New: gnome-screensaver fails to unlock if fingerprint reader device is busy
https://bugzilla.novell.com/show_bug.cgi?id=448166 Summary: gnome-screensaver fails to unlock if fingerprint reader device is busy Product: openSUSE 11.1 Version: Beta 5 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: thoenig@novell.com ReportedBy: thoenig@novell.com QAContact: qa@suse.de CC: rodrigo@novell.com Found By: --- gnome-screensaver fails to unlock if fingerprint reader device is busy If the USB device is busy/not accessible it's impossible to unlock the screensaver. I've got a patch ready. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448166 User thoenig@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=448166#c1 --- Comment #1 from Timo Hoenig <thoenig@novell.com> 2008-11-24 05:57:55 MST --- Created an attachment (id=254754) --> (https://bugzilla.novell.com/attachment.cgi?id=254754) updated patch Rodrigo, that's the updated patch. It adds some sanity checks and doesn't bail out with exit(1) if fp_init() fails. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448166 User thoenig@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=448166#c2 --- Comment #2 from Timo Hoenig <thoenig@novell.com> 2008-11-24 06:00:48 MST --- $ osc sr show -d 3964 quilt somewhat broke the patch, sorry for that. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448166 User thoenig@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=448166#c3 Timo Hoenig <thoenig@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #3 from Timo Hoenig <thoenig@novell.com> 2008-11-24 06:08:28 MST --- Hm, I just realized that it will need some more checks. Will post an update once done. I've revoked the submit request for the time being. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448166 User thoenig@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=448166#c4 Timo Hoenig <thoenig@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #254754|0 |1 is obsolete| | --- Comment #4 from Timo Hoenig <thoenig@novell.com> 2008-11-25 01:49:54 MST --- Created an attachment (id=255071) --> (https://bugzilla.novell.com/attachment.cgi?id=255071) updated patch (2) OK. This one was nasty. The problem was that gnome-screensaver-dialog didn't appear after moving the mouse. That happens on all systems where (a) a supported fingerprint reader device is present (b) the user hasn't acquired a fingerprint It turned out that it perfectly works if gnome-screensaver is being run with --debug --no-daemon but failed in normal operation. After scratching my head for a couple of hours I found out that there is some evil stuff going on. gnome-screensaver-finger-print.patch contains a couple of fprintf statements fprintf (stderr, ...) Those statements cause the problem. I didn't dig any deeper to find out what is wrong with stderr when running in normal operation. There should be a big warning in gnome-screensaver-dialog.c not to use fprintf on stderr if one doesn't want to get in trouble. I've updated my patch and created a submit request. $ osc sr show -d 3980 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com