Red Hat Bugzilla – Bug 406011
DPMS only turns monitor off half the time
Last modified: 2009-06-30 19:41:06 EDT
Description of problem:
I'm not sure I've assigned this to the right component or not so please
re-assign if appropriate.
I'll attach my xorg log but I'm using some sort of ATI card connected to two
monitors. I'm running KDE and xset -q reports:
DPMS (Energy Star):
Standby: 720 Suspend: 1800 Off: 3600
DPMS is Enabled
Monitor is On
The problem is that half the time I come in to work and find the monitors are
still on, showing what appears to be a frozen screensaver. If I login from a
remote machine and run xset -q from there it reports: "Monitor is Off" which it
clearly is not.
Version-Release number of selected component (if applicable):
not, seems random
Steps to Reproduce:
1. Start KDE Control Center
2. Open Peripherals
3. Click Display
4. Click Power Control tab
5. Turn on Enable display power management
6. Set Standby to 12 min, Suspend to 30, Power off to 60
7. Click Apply
8. Let computer set idle for a while
Sometimes the monitors will power off at the expected time. Sometimes they do
not, instead showing what appears to be a frozen screensaver even though 'xset
-q' reports that the monitors are off.
Monitors always turn off.
Created attachment 273951 [details]
Thanks for the bug report. We have reviewed the information you have provided
above, and there is some additional information we require that will be helpful
in our diagnosis of this issue.
Please attach your X server config file (/etc/X11/xorg.conf) to the bug report
as individual uncompressed file attachment using the bugzilla file attachment
Could you please also try to run without any /etc/X11/xorg.conf whatsoever and
let X11 autodetect your display and video card? Attach to this bug
/var/log/Xorg.0.log from this attempt as well, please.
We will review this issue again once you've had a chance to attach this information.
Thanks in advance.
Created attachment 293907 [details]
Created attachment 293908 [details]
Xorg.0.log when no xorg.conf is present
does this happen with the latest F8 of F9 ati drivers still?
It is either not happening at all anymore or it has become much more infrequent.
Either way I'm happy with its behavior now.