[Mageia-dev] Desktop monitor powering down

[Frank Griffin]

On 08/08/2012 07:42 AM, Colin Guthrie wrote:
> Generally speaking these settings are done in the display environment
> GUIs (i.e. Gnome and KDE) thus avoiding having to call xset directly by
> the user or in scripts etc. This is just a command line interface to
> things the DE's should wrap already.
>
> So I'd go looking for those bits breaking and/or something in your user
> account messing up. i.e. try it with a fresh boot and logging into a
> fresh user account and see if the problem still occurs. That might help
> narrow down where the real problem lies.
>
>
This is getting muddy.  I've done a lot of cauldron updating since my 
last logout/reboot, and when I tried a fresh boot GDM hung repeatedly, 
and I had to switch to KDM.

The problem doesn't occur with a fresh user, but it no longer occurs on 
my userid either.  Either it's a function of the DM, or else the "xset 
-dpms" I did previously is sticky:

[root at ftgme2 ftg]# xset q
Keyboard Control:
...
DPMS (Energy Star):
   Standby: 600    Suspend: 600    Off: 600
   DPMS is Disabled

But knowing that dpms is involved got some google results, and I think 
the problem is https://bugs.kde.org/show_bug.cgi?id=295814

The similarity between my case and the reported ones is that I had set 
all Power Management off, so that the screen would never dim or 
disable.  I had done this because I have some WINE stuff run overnight 
by cron, and when KDE blanks or disables the screen, graphical apps 
won't start.

According to the report, a disabled PM enables dpms with a random set of 
numbers.  I just happened to get 30 seconds.  One poor sod had a 
1-second timeout.