[Bug 13199] Monitor turns off when internal screensaver is activated

[bugzilla-daemon at freedesktop.org]

http://bugs.freedesktop.org/show_bug.cgi?id=13199


gsr.bugs at infernal-iceberg.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |gsr.bugs at infernal-
                   |                            |iceberg.com




------- Comment #1 from gsr.bugs at infernal-iceberg.com  2007-11-14 12:57 PST -------
I was going to report the same thing, as old behaviour was pretty nice:
"xset s 300 300": make the screen go black in 5 minutes
"xset dpms 600 600 600": and then make it turn off in another 5 (10 from start)

Now "s" will let you choose between off with "xset s blank" or the
moire inducing cross pattern with X logo with "xset s noblank", but
no way to make it black but still give time to avoid a start/stop cycle.

Old behaviour, even if what the man page says contradicts it, was
the most complete (if I want animations eating CPU, even if slow, I
will install xlock, xscreensaver or something like that, which I just
had to do to get a black screensaver). New behaviour forces CRT tubes
and LCD backlights a bit too much without option to have the two phase
power off. And in the case of CRTs, it is even worse, as I doubt a high
frequency pattern is nice for the driving circuits (at least I saw it
moves slightly, so no burn in if using fast cycle time as "xset s 300 30").

A less extreme pattern would be better (or even just show the X logo in
faded colours, without any bg pattern), if there is no way to go back to
"s makes screen black". Yes, I tried "xset dpms 100 900 900" to test if
first level would be OK, but it seems this monitor does the same for
all modes.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.