registry team mailing list archive

Thread
Date

[Bug 460375] Re: Display goes black after 10 minutes idle despite "never" settings

To: registry@xxxxxxxxxxxxxxxxxxx
From: "Psy\[H\[\]" <460375@xxxxxxxxxxxxxxxxxx>
Date: Mon, 08 Nov 2010 10:17:12 -0000
Reply-to: Bug 460375 <460375@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

situation in Maverick:
In X:
default screen blanking timeout  is 600s if no screensaver app is used.
gnome-screensaver, configured to be off, successfully sets timeout to 0.
gnome-power-manager works as it should.

so, with the exception of strange hard-coded  600s timeout, everything
is fine.

In console:
virtual terminals have their own blanking timeout, also set to 600s, (that can be changed with setterm). This is really annoying, imagine situation:
user has 2TB hdd, a routine check on startup is in progress, progress bar is displayed. It takes more than 10 minutes. Screen switches off leaving user with no indication of the process. Pressing some key to restore screen will result in canceling check.

Wouldn't it be more logical to implement a principle "if there is no
explicit screensaver/blanking/screenoff is in place, then do not
blank/turn off screen by default". This goes to default X settings and
VT settings.

-- 
Display goes black after 10 minutes idle despite "never" settings
https://bugs.launchpad.net/bugs/460375
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for NULL Project.