Bug 170478

Summary:	[DPMS] the screen is not shutdown at all when i set a screensaver
Product:	[Unmaintained] kscreensaver	Reporter:	solsTiCe <solstice.dhiver>
Component:	general	Assignee:	kscreensaver bugs tracking <kscreensaver-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	wade.nels
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description solsTiCe 2008-09-05 20:51:57 UTC

Version:            (using KDE 4.1.1)
OS:                Linux
Installed from:    Unlisted Binary Package

when i set a screensaver and check start automatically in x minutes 
and also set a time greater than the previous one (y >= x+1) at which the screen must shutdown in DPMS settings (energy saving) in system setting, the screen is not blanked (shutdown, put in stand by mode)

but if i set no screensaver by unchecking in desktop -> screensaver -> start automatically screensaver in x minutes
the screen is shutdown at y minutes.

it seems to be a regression introduce in kde 4.1.1. 
it was working  in kde 4.1 i think

Comment 1 Wade Nelson 2008-11-24 15:47:47 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 2 Lubos Lunak 2009-01-27 14:43:12 UTC


*** This bug has been marked as a duplicate of bug 165265 ***