Hardware: http://www.smolts.org/client/show/pub_147a1a2f-5adb-4d82-8a2a-fdd35783929b Following instructions at: https://fedoraproject.org/wiki/QA:Testcase_intelvideo_dpms Afer 20 mins the screensaver is still active.
Same here, but if I ssh in and run: DISPLAY=:0.0 xset dpms force off the display powers down, as expected. Maybe this is a problem in GNOME, and not the intel driver?
Same here, http://www.smolts.org/client/show/pub_2fcec018-0916-4232-bb21-82f25e2d64f0 Waiting doesn't work, xset dpms does.
ditto, http://www.smolts.org/client/show/pub_8adb55a6-5ecb-46bd-a458-8bce0b93769b
same here, http://www.smolts.org/client/show/pub_e5adecb3-9df6-4355-9dfc-a5622c85dc7f In my case I booted with the "nomodeset" option (in contrast to the Test-case instructions), because of #488980. So this problem, I think, is NOT dependent on kernel-mode-setting.
Ditto, http://www.smolts.org/client/show/pub_112457b8-dcf7-4ddb-a1c7-c90b3c821ac3
Still present in rawhide as of 2009-03-27.
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, if available) and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below. Could you please also try to run without any /etc/X11/xorg.conf (if you have one) 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.
for me (comment #3), I reproduced with no xorg.conf
for me (comment #4), it now seems more like a Gnome bug. I only have this problem when I'm logged in. I've found that at the GDM login screen, the monitor power-saving feature works just fine, with or without KMS enabled. I wait 10 minutes, and it goes to power-save mode, and then recovers from it, every time. I am running without an xorg.conf. Since it does not seem to be a problem with the X server for me, I'm not going to bother capturing an Xorg.0.log file, sorry.
I believe we found during the Radeon test day yesterday that it's actually known that GNOME's handling of DPMS is currently broken, and the test case was replaced with a different one: https://fedoraproject.org/wiki/QA:Testcase_radeon_dpms can you try that test on Intel and see if it works? If so, then the problem is the one in GNOME, which is I believe already reported.
Ok, since I ran the F11 intel test-day ISO, there wouldn't have been an xorg.conf file so I suspect the Gnome/DKMS issue is at fault here too.
I've re-written the DPMS handling in gnome-power-manager in trunk last week, as it's horribly broken in rawhide at the moment. Could somebody try out the trunk code of gnome-power-manager please, and tell me if that fixes things. If it works okay, I'll backport to stable. Thanks.
(In reply to comment #12) > I've re-written the DPMS handling in gnome-power-manager in trunk last week, as > it's horribly broken in rawhide at the moment. Could somebody try out the trunk > code of gnome-power-manager please, and tell me if that fixes things. If it > works okay, I'll backport to stable. Thanks. And I think you should be rewarded with this bug. Reassigning.
This is in rawhide now: * Tue Apr 21 2009 Richard Hughes <rhughes> - 2.26.1-1 - Update to 2.26.1 - Fix the low capacity warning to fix rh#489832 - Backport DPMS and IDLETIME fixes from master to fix multiple bugs - Connect to gnome-session and exit on logout - Remove upstreamed patches