Hide Forgot
Description of problem: When my computer is inactive for 50s, the screen turns blank. I have no screensaver active at all and the system is not set 'performance', so the screen should not turn off. I noticed that this is the result of the energy-star power management which turns off the screen after 50s. (output of xset q) DPMS (Energy Star): Standby: 50 Suspend: 75 Off: 100 DPMS is Enabled Monitor is On This is weird as I placed in xorg.conf the following lines Section "ServerFlags" Option "blank time" "0" Option "standby time" "0" Option "suspend time" "0" Option "off time" "0" Option "dpms" "false" EndSection Hence, dpms should be disabled, however it is not. Version-Release number of selected component (if applicable): $ Xorg -version X.Org X Server 1.11.4 Release Date: 2012-01-27 X Protocol Version 11, Revision 0 Build Operating System: x86-01 2.6.32-220.4.1.el6.x86_64 Current Operating System: Linux toaster.basestar.cy 3.2.6-3.fc16.x86_64 #1 SMP Mon Feb 13 20:35:42 UTC 2012 x86_64 Kernel command line: BOOT_IMAGE=/vmlinuz-3.2.6-3.fc16.x86_64 root=UUID=042b488e-c463-4c75-ac4d-8c8a7ab01caf ro rd.md=0 rd.lvm=0 rd.dm=0 KEYTABLE=us quiet SYSFONT=latarcyrheb-sun16 rhgb rd.luks=0 LANG=en_US.UTF-8 Build Date: 08 February 2012 10:54:57PM Build ID: xorg-x11-server 1.11.4-1.fc16 Current version of pixman: 0.22.2 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. How reproducible: always Steps to Reproduce: 1.log into kde 2.wait 3. Actual results: The screen turns blank after 50s Expected results: I would expect this result under powersave mode. In performance mode, I expect that these numbers should be much higher (10min or so) or turned off. Furthermore, xorg.conf states that dpms is turned off, however it is not. I would also expect it to be turned off. Additional info: A workaround I found was typing xset -dpms
does it happen if you don't log in to KDE? my guess is KDE is setting this up and overriding the conf file.
The KDE (PowerDevil) settings can be customized in KDE System Settings.
It is true that most settings can be done with KDE System settings, however they do not affect this. There is no reference to 50 s in there. When I do xset -dpms, dpms never turns on anymore, even after reboot. Only a certain kde update turns the dpms back on. I believe it is xsettings-kde, but I cannot confirm this 100%.
upstream bug https://bugs.kde.org/show_bug.cgi?id=295164 seem related
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.