gnome-screensaver doesn't follow setting to increase blank screen interval

Bug #501518 reported by androith
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
One Hundred Papercuts
Invalid
Undecided
Unassigned
gnome-screensaver (Ubuntu)
Invalid
Low
Ubuntu Desktop Bugs

Bug Description

1. Go to screensaver preferences through the standard Ubuntu menu.
2. Increase the blank screen period to 2h (which is the maximum, there is sadly no way to disable screen blanking, even in the power management settings).
3. Watch youtube.com video and be annoyingly interrupted by a blank screen after 10 minutes.

Revision history for this message
Omer Akram (om26er) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

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

Are you sure you're not hitting the GNOME power management blank screen timeout?

Open System/Preferences/Power Management, and take a look at the "Put display to sleep when inactive for" settings on the AC Power and the On Battery Power tabs.

This is different than the gnome-screensaver timeout.

Revision history for this message
androith (androith) wrote :

Yeah, I'm sure. Those two are never/never. Let me see if, in the next few days, the bug persists in my current gnome-screensaver version and submit it upstream if so (or suggest a close otherwise).

Revision history for this message
Dylan McCall (dylanmccall) wrote :

I have a hunch here, but no hardware to test it right now. Could you try hitting the Set Default button (and follow the prompt to set that as system-wide default), and let us know if that changes the situation?

Revision history for this message
Vish (vish) wrote :

Marking incomplete. Awaiting submitters response.

Changed in gnome-screensaver (Ubuntu):
status: New → Incomplete
Revision history for this message
Vish (vish) wrote :

Thank you for bringing this bug to our attention. However, a paper cut should be a small usability issue, in the default Ubuntu install, that affects many people and is quick and easy to fix. So this bug can't be addressed as part of this project.

- This is a bug and not a papercut.
For further information about papercuts criteria, please read https://wiki.ubuntu.com/PaperCut.

Don't worry though, this bug has been marked as "Invalid" only in the papercuts project.

Changed in hundredpapercuts:
status: New → Invalid
Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Is gnome-screensaver even running (what is the output of "ps aux | grep gnome-screensaver")? If it is not running, then you might be hitting the timeout of the built-in Xorg screensaver, which gnome-screensaver normally disables. If it is, then please kill it, and run:

gnome-screensaver --debug --no-daemon 2>&1 | tee gnome-screensaver.log

Let the screen blank as usual after 2 minutes, and then attach the resulting log file to this bug report

Changed in gnome-screensaver (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
importance: Undecided → Low
Revision history for this message
Chris Coulson (chrisccoulson) wrote :

I mean, "after 10 minutes" in my last comment there

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

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to 'New'. Thanks again!

Changed in gnome-screensaver (Ubuntu):
status: Incomplete → Invalid
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.