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 603705 - Screensaver does not activate.
Screensaver does not activate.
Status: RESOLVED OBSOLETE
Product: gnome-screensaver
Classification: Deprecated
Component: daemon
2.28.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-screensaver maintainers
gnome-screensaver maintainers
Depends on:
Blocks:
 
 
Reported: 2009-12-03 16:30 UTC by Cornwall
Modified: 2014-08-20 20:23 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
gnome-screensaver patch. (3.67 KB, patch)
2010-07-06 13:59 UTC, Cornwall
none Details | Review
Adjust the mechanism in _gs_monitor_update_from_prefs(). (3.44 KB, patch)
2011-06-28 15:23 UTC, Shih-Yuan Lee (FourDollars)
none Details | Review

Description Cornwall 2009-12-03 16:30:28 UTC
>>From the Launchpad report:

Binary package hint: gnome-screensaver

When I boot with the screensaver not activated and then activate the screensaver, the screen starts to fade but then immediately returns to the desktop instead of starting the screensaver.

As a workaround I can watch the preview or I have to reboot. After these activities the screensaver works fine.

ProblemType: Bug
Architecture: amd64
Date: Thu Dec 3 15:51:56 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: gnome-screensaver 2.28.0-0ubuntu3
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-15.50-generic
SourcePackage: gnome-screensaver
Uname: Linux 2.6.31-15-generic x86_64
XsessionErrors:
 (gnome-settings-daemon:2482): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:2482): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (nautilus:2583): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (polkit-gnome-authentication-agent-1:2622): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (alltray:2608): Gdk-WARNING **: gdk_window_set_user_time called on non-toplevel
Comment 1 Cornwall 2009-12-03 16:31:27 UTC
On a similar note, half of the time my computer does not turn the monitor off. Instead of blanking the screen, it puts an icon in the notification tray until I move the mouse to "wake" it.
Comment 2 Marc Deslauriers 2009-12-10 00:44:25 UTC
Here is the Ubuntu bug report:

https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/491926

I suspect gnome-screensaver is starting too early. If I add --debug to /etc/xdg/autostart/gnome-screensaver.desktop, or put a wrapper around /usr/bin/gnome-screensaver, the problem goes away.
Comment 3 William Jon McCann 2010-01-29 02:44:57 UTC
I don't really understand the issue.  Can you reiterate the exact behavior you are seeing and a set of steps to reproduce it?  Thanks.
Comment 4 Tobias Mueller 2010-06-10 09:27:16 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!
Comment 5 rlange 2010-07-06 06:06:39 UTC
I think this is related to another bug described in Launchpad.

https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/241206

Note that I have made a detailed diagnosis and patches in comments 16 and 17 of that bug report.  The patches are against Ubuntu source packages, but I would be willing to patch them against the current source.  Any help to speed that work up would be appreciated, since I have not contributed directly to Gnome projects before, so I don't know the procedures and culture.

Note: this bug affects both gnome-screensaver and gnome-session, since there is a bit of coupling between the two projects.
Comment 6 Cornwall 2010-07-06 13:59:18 UTC
Created attachment 165359 [details] [review]
gnome-screensaver patch.

Robert Lange's patch.
Comment 7 Cornwall 2010-07-06 14:00:26 UTC
I've taken the liberty of attaching the launchpad report's patch upstream. I'm unable to test right now, will ask LP people to test.
Comment 8 rlange 2010-10-07 02:48:10 UTC
Any updates on the status of this bug?  The sooner it gets fixed, the sooner we can put behind us the worries about security issues and physical damage to monitors.  I know the patch is a fairly involved one, but the logic is fairly straightforward and I would be happy to explain it further to someone, if that is the issue.
Comment 9 Shih-Yuan Lee (FourDollars) 2011-06-28 15:23:03 UTC
Created attachment 190877 [details] [review]
Adjust the mechanism in _gs_monitor_update_from_prefs().

This patch may be able to solve this problem.
I also prepare https://launchpad.net/~fourdollars/+archive/gnome-screensaver for Ubuntu 10.10/11.04 users.
Please help to review this patch, thanks.
Comment 10 rlange 2012-11-01 13:21:36 UTC
For the last couple of releases I have not been able to reproduce the bug, at least on Ubuntu.  Unless others are still able to reproduce the bug on the current version, I would recommend closing it.
Comment 11 Bastien Nocera 2014-08-20 20:23:18 UTC
The screen lock is now implemented directly in gnome-shell, not in
gnome-screensaver (as it was with older version of GNOME 3 and GNOME 2.x).

If the reported problems persists in recent versions of GNOME, please file a new bug against gnome-shell with the "lock-screen" component selected.

If your installation is an older version of GNOME that cannot be upgraded (such as an enterprise version), please use the appropriate support mechanism from your vendor, or your distribution instead.