gnome-screensaver fails to run right after being activated

Bug #494114 reported by tekstr1der
4
This bug affects 1 person
Affects Status Importance Assigned to Milestone
GNOME Screensaver
Unknown
Unknown
gnome-screensaver (Ubuntu)
Confirmed
Undecided
Marc Deslauriers

Bug Description

Binary package hint: gnome-screensaver

Screensaver correctly initiates following the timeout period set in the screensaver configuration panel. The display fades to black then immediately snaps back to full brightness. The selected screensaver is never displayed.

ProblemType: Bug
Architecture: i386
Date: Tue Dec 8 12:26:48 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: wl
Package: gnome-screensaver 2.28.0-0ubuntu3.1
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-16.52-generic
SourcePackage: gnome-screensaver
Uname: Linux 2.6.31-16-generic i686

Revision history for this message
tekstr1der (tekstr1der) wrote :
Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

Thanks for filing this new bug.

If you select "Blank Screen", does it work?

Revision history for this message
tekstr1der (tekstr1der) wrote :

Thanks for getting on this so quickly.

If you are referring to the screensaver setting of "Blank Screen", no, it exibits the same behavior regardless of which screensaver is selected. Also they all run successfully in Preview mode.

If you are referring to the "Blank Screen" setting in power management panel, yes dpms power saving works as expected.

Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

What desktop environment does this problem occur in? (GNOME, XFCE, KDE, etc.)
Do you use visual effects? (System/Preferences/Appearance/Visual Effects)
Is this a laptop or a desktop machine?
How many monitors do you use?
If it is a laptop, do you use an external screen?

Could you please also run the following command and attach the resulting file here:

gconftool-2 --dump /apps/gnome-screensaver /desktop/gnome/session /desktop/gnome/lockdown > debug.xml

Revision history for this message
tekstr1der (tekstr1der) wrote :

This is under Gnome
compiz is enabled
Netbook
1 monitor
no external screen

Attached output from gconftool-2 --dump /apps/gnome-screensaver /desktop/gnome/session /desktop/gnome/lockdown > debug.xml

Revision history for this message
tekstr1der (tekstr1der) wrote :

Also, I should add that the screensaver does function properly when started with

gnome-screensaver --debug --no-daemon

I've attached the output from that as well.

Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

If you disable desktop-effects (System/Preferences/Appearance/Visual Effects/None) and reboot, does it work?

Revision history for this message
tekstr1der (tekstr1der) wrote :

I would like to note the following behavior:

1) enable the screensaver via checkbox in screensaver preferences
2) for duration of session, note same behavior described in this bug report
3
) leaving the option enabled, reboot
4) following boot and subsequent reboots, screensaver functions as expected.

This isolates the bug to the following STR:

1) disable screensaver via checkbox in screensaver preferences
2) reboot
3) enable the screensaver via checkbox in screensaver preferences
4) for duration of session, note same behavior described in this bug report

Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

Thanks for discovering that! I can reproduce the problem with the steps you've described.

Changed in gnome-screensaver (Ubuntu):
status: New → Confirmed
Revision history for this message
tekstr1der (tekstr1der) wrote :

I didn't want to disable compiz to test this as I don't really care about having a screensaver, more about a fully functional system. So, I created a new user and followed the STR. I can reproduce the exact issue following the above steps.

I then disabled desktop effects on the new user, rebooted, enabled the screensaver and yes, it is now functional. It seems compiz is indeed playing a role in this bug.

Having multiple workarounds now is better than nothing. Also are you able to reproduce this following the above steps with compiz enabled? If not and it's just me, I will mark this bug invalid. This is a system upgraded from intrepid to jaunty to karmic alpha 2 thru current karmic updates all the while with the same main user profile. I have verified this bug does not exist on a fresh VM install.

Revision history for this message
tekstr1der (tekstr1der) wrote :

Oops sorry, didn't see you already reproduced it. That's good. Also, I've not really ruled this out on a fresh install as I never did enable compiz in the virtual machine and that seems to make all the difference. Looks like a valid bug after all. Let me know if there is any other info / debugging I can provide. Thanks.

Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

I can reproduce the problem without compiz.

summary: - gnome-screensaver fails to run
+ gnome-screensaver fails to run right after being activated
Changed in gnome-screensaver (Ubuntu):
assignee: nobody → Marc Deslauriers (mdeslaur)
Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

Well, this is fun: as soon as I add "--debug" to /etc/xdg/autostart/gnome-screensaver.desktop, I can't reproduce the issue anymore.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.