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 576463 - can't unlock screen after upgrade until restarting gnome-screensaver
can't unlock screen after upgrade until restarting gnome-screensaver
Status: RESOLVED FIXED
Product: gnome-screensaver
Classification: Deprecated
Component: dialog
2.26.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-screensaver maintainers
gnome-screensaver maintainers
Depends on:
Blocks:
 
 
Reported: 2009-03-23 18:30 UTC by Sebastien Bacher
Modified: 2009-08-21 02:58 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26

Attachments
Patch which fixes the issue (1.52 KB, patch)
2009-06-29 21:51 UTC, Chris Coulson 		none Details | Review

Description Sebastien Bacher 2009-03-23 18:30:07 UTC 
* install gnome-screensaver 2.24
* start a session
* upgrade to 2.26
* lock the screen
* you can unlock the screen, you get a flickering screen but not password entry displayed
Comment 1 Sebastien Bacher 2009-03-23 18:31:18 UTC 
not sure what informations would be useful there that's easy to trigger and happen in a consistent way on different hardware, gnome-screensaver --debug has no obvious error
Comment 2 Chris Coulson 2009-06-28 22:51:27 UTC 
This is happening because gnome-screensaver-dialog deprecated the "--away-message" option after 2.24 (and replaced it with a "--status-message" option). This means that spawning a 2.27.x gnome-screensaver-dialog from a 2.24.x gnome-screensaver process fails, because it still passes the --away-message option, and appears to be what is happening here.
Comment 3 Chris Coulson 2009-06-29 21:51:24 UTC 
Created attachment 137589 [details] [review]
Patch which fixes the issue

Here is a patch applied in Ubuntu to resolve this issue on upgrade
Comment 4 William Jon McCann 2009-08-21 02:58:39 UTC 
I've committed a patch that will ignore the option.  Thanks.