Bug 165265 - Monitor is not turned off by power management if screen saver is running
Summary: Monitor is not turned off by power management if screen saver is running
Status: RESOLVED FIXED
Alias: None
Product: kscreensaver
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: kscreensaver bugs tracking
URL:
Keywords:
: 156605 165368 170478 180104 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-06-29 03:02 UTC by Marcelo Sales
Modified: 2010-02-12 10:15 UTC (History)
15 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marcelo Sales 2008-06-29 03:02:51 UTC
Version:            (using KDE 4.0.83)
Installed from:    Fedora RPMs
OS:                Linux

If a screen saver is running, the monitor will not be turned off after the time specified in power management configuration.
However, if no screen saver is configured to start or if the time specified in power management for shutting down the monitor is lesser then the time to initiate the screensaver, then the monitor is turned off correctly.
I've tested with several screen savers (blank screen, glmatrix, science and others), always with the same result.
Comment 1 Henrik Hudson 2008-09-28 10:52:15 UTC
version: 4.1.1 via ports
os: freebsd 7.1-prerelease

I noticed this under the last Kubuntu 4.1.1 I had installed, but the problem still occurs under BSD.

I have DPMS enabled for my monitor in xorg.conf and selecting / enabling  "Power Management" in the control panel doesn't actually do anything. The screen saver runs forever and the monitor never turns off. I haven't tested whether or not the monitor will turn off if the screen saver is not enabled, but I will do so.
Comment 2 Marcelo Sales 2008-09-28 17:30:14 UTC
I confirm the problem still occur with KDE 4.1.1 (Fedora 9). Just for the record, this did not happen on KDE 4.0.x, the monitor was turned off correctly then.
When I first reported the problem I was using an nvidia video card. Now I'm using Intel video, but nothing has changed.
Comment 3 Magnus Kessler 2008-10-16 08:14:49 UTC
version: 4.1.2
os: gentoo linux

The issue still occurs on 4.1.2.
Comment 4 Kenyon Ralph 2008-10-23 05:48:15 UTC
This bug is possibly a duplicate of Bug #165368.
Comment 5 Wade Nelson 2008-11-24 15:47:42 UTC
I can confirm this, on my laptop (Dell Inspiron B130, all Intel hardware) I can produce the following problems with the following procedures:

1) Enable screensaver with or without lock after time X
2) Close laptop -> LCD backlight turns off
3) After a second or so LCD backlight turns back on and screensaver is running

1) Enable screensaver to activate after X minutes
2) Enable Display Power Management to do *anything* after X+1 minutes
3) Display remains on with screensaver running, i.e. Display Power Management Settings have no effect.

I can reproduce this under KDE 4.1.3 on Debian Lenny with KDE4 backport (http://kde4.debian.net) and also under KDE 4.1.2 on Slackware-current.

I think perhaps Bug 156605 , Bug 165265 , Bug 170478 , and Bug 165368 all relate back to the same DPMS+screensaver=no_worky issue.
Comment 6 Thorsteinn A. Malmjursson 2008-12-05 22:43:47 UTC
This bug does not exist on KDE 4.1.2 running on Mandriva 2009.0 - the DPMS works fine, and screensavers do drop to standby, suspend or poweroff whilst the DPMS is in use.  My controls for the service in SystemSettings work perfectly and operate the system as needed.
Comment 7 Marcelo Sales 2008-12-05 22:51:24 UTC
For me, it still exists in KDE 4.1.3 running on Fedora 10. The monitor is not turned of if screensaver is running.
Comment 8 Caleb Cushing 2008-12-05 22:52:36 UTC
I'm not sure if it's this bug specifically that I'm experiencing but I know kde won't shut the monitor off but xset dpms force off works. is there a dcop call I can run to manually test kde?
Comment 9 Alex Dioso 2008-12-08 08:43:18 UTC
*** This bug has been confirmed by popular vote. ***
Comment 10 Andriy Rysin 2009-01-04 18:38:29 UTC
I can confirm this on KDE 4.1.87 (compiled from sources - 20090101) on my Mandriva 2009 and Cooker.

It seems that if DPMS timeout setting for standby is less or equal to the screensaver timeout then the screen blacks out ok (backlight is off) but if screensaver kicks in before DPMS or if screensaver is turned on manually (e.g. by moving mouse to the corner with appropriate setting on) then DPMS is never applied and backlight is always on.
Comment 11 David Bailey 2009-01-12 01:11:26 UTC
Confirm problem exists in openSUSE 11.1 / KDE 4.1.3
Comment 12 David Bailey 2009-01-12 01:13:13 UTC
NOTE: Because LCD monitor backlights have a lifespan before failure, this problem causes damage to hardware. For instance, having a backlight left on overnight over a period months will definitely cause the brightness to dim compared to a screen which is not subjected to this problem.
Comment 13 Lubos Lunak 2009-01-27 14:40:10 UTC
Fixed for 4.2.1.
Comment 14 Lubos Lunak 2009-01-27 14:41:26 UTC
*** Bug 165368 has been marked as a duplicate of this bug. ***
Comment 15 Lubos Lunak 2009-01-27 14:43:12 UTC
*** Bug 170478 has been marked as a duplicate of this bug. ***
Comment 16 Lubos Lunak 2009-01-27 14:55:39 UTC
*** Bug 156605 has been marked as a duplicate of this bug. ***
Comment 17 whashnez 2009-03-01 04:25:00 UTC
You mean that in kde 4.2.1 this problem will be resolved?
Comment 18 Magnus Kessler 2009-03-01 11:48:01 UTC
(In reply to comment #17)
> You mean that in kde 4.2.1 this problem will be resolved?

Yes, the fixes went into SVN at the end of January. See http://lists.kde.org/?l=kde-commits&m=123298285600590&w=2 and the next two commits.
Comment 19 Caleb Cushing 2009-06-08 00:53:35 UTC
I think this has regressed in 4.2.4 my screen is no longer shutting off.
Comment 20 John Horne 2009-07-06 22:34:34 UTC
Works fine for me.
Fedora 11, KDE 4.2.4.
Comment 21 Caleb Cushing 2009-07-07 05:16:24 UTC
yeah. this hasn't regressed I've another bug open where it's intermittent. I was just having a lot of problems with that. come to think of it could be an intel driver problem... I haven't noticed it in a week since I upgraded to the development driver.
Comment 22 Oswald Buddenhagen 2010-02-12 10:15:19 UTC
*** Bug 180104 has been marked as a duplicate of this bug. ***