Version: (using KDE KDE 3.5.1) Installed from: SuSE RPMs OS: Linux I have had this problem since 3.3 or so, it has been annoying, but haven't found a workaround today... Normaly I set my DPMS settings in Kontrolzentrum->Angeschlossene Geräte->Anzeige (Control Centre->Conntected Devices->Display I think in English) to 60, 90 and 120 minutes for Stand-by, Suspend and Off respectively. The Screensaver is set to 30 minutes. After around 10 minutes of inactivity, the monitor shuts down... The screensaver seems to be working correctly, in that if I tap a key before 30 minutes the monitor switches back on and the desktop appears, if I tap a key after 30 minutes the screensaver pops up and asks me for a password. Using xset dpms followed by the relevant values works for the current session, but restarting KDE or rebooting the PC resets to the 10 minute stand-by. Today, I was writing a message for the suse newsgroup and a thought crossed my mind, I then reset the timeouts to 45, 50 and 59 minutes and they seem to be working correctly now. It looks like there might be a problem with Control Centre setting the dpms values correctly when they are over 1 hour, even though values over 1 hour can be selected. Hardware: Asus motherboard (not sure on model number, can open case and report it if important) Athlon XP2100+ 1GB DDR400 RAM Aeolus FX5700LE 256MB graphics card Iiyama 17" TFT on DVI port Hyundai Image Quest Q17 on VGA port (same problem occurs when using a single monitor on DVI as well) This is running with the KDE RPM's supplied by Novell/SUSE with SUSE Linux 9.1, 9.2, 9.3 and 10.0 and currently Xorg 6.8. Currently running KDE 3.5.1 from the supplementary RPM's from the SUSE mirror.
Hmm, after rebooting today, the problem has started again, with settings under 1 hour. Going into Control Centre and changing the settings (move stand-by 1 minute forward and then apply makes it work again... Starting to sound like CC isn't sending the settings to X when logging in?
New observation: I am currently beta testing SUSE Linux 10.1 Beta 4. When I installed that and left it with the generic nv driver on a spare machine, the DPMS settings worked correctly. Today I finally got around to installing the nVidia proprietary driver and the DPMS settings problem has raised its head. So it looks like the way the energy saving mode information is sent to the driver is working fine for the OSS nv driver, but not for the nvidia driver. Is this now a control centre problem, or should we raise a bug report with nVidia?
This is still happening with the nvidia drivers under KDE 3.4, 3.5.1 and 3.5.2. I've also noticed that it is the same with the ATi fglrx drivers on my laptop.
And using KDE 3.5.10 on a more recent system? Do you still have this issue?
@David: can you still reproduce this issue?
The Energy KCM has been outdated and unmaintained since some time ago. In the other hand, KDE4 gained a new (and powerful) power management daemon: "PowerDevil" (which is accessible from System Settings/Advanced/Power Management) Today we removed the Energy KCM from the code in KDE 4.4 development trunk, to avoid some conflicts between the settings of the two modules and to set PowerDevil as the default power manager (it was the default one already). To the people using KDE4: disable the Energy KCM settings and configure your power management options using the new PowerDevil. If you encounter the same problems, please file new bug reports against the "solid/powerdevil-daemon" product on bugs.kde.org Thank you.