Bug 230227

Summary:	Monitor screen become blank inspite of powerdevil settings
Product:	[Unmaintained] solid	Reporter:	Pavel Baranchikov <maednoldor>
Component:	powermanagement-daemon	Assignee:	Dario Freddi <drf>
Status:	RESOLVED FIXED
Severity:	normal	CC:	algspd, anvariom, arguri, cespinal17, ingo.gb, rastavibes
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Pavel Baranchikov 2010-03-10 18:27:06 UTC

Version:            (using KDE 4.4.1)
OS:                Linux
Installed from:    openSUSE RPMs

I set up presentation power schema. I can leave powerdevil running or turn it off.

In some time (possible 15-20 minutes) monitor screen becomes blank. Monitor does not go to stand-by mode (power led is on, not blinking).

KDE 4.4 has broke the 'disable screensaver' option in SMPlayer, so my only way was using of presentation power schema.

No other power daemons are not loaded (as I suppose).

Comment 1 ingo 2010-03-13 09:09:04 UTC

Ditto on up-to-date 64-bit ArchLinux with vanilla KDE4.4.1. 

Steps taken so far: turned off powerdevil and made sure no other power managers are running. KDE still turns the screen off rather than keeping the screensaver on indefinitely.

And there is no way of turning the screen on again but manually turning it off and on again.

Comment 2 arguri 2010-03-24 19:27:40 UTC

Same on Gentoo. Either PowerDevil is not able to overwrite DPMS default settings, ignores the user settings, or something else.

Pavel: As an intermediate "solution" try to turn off dpms via "xset -dpms". Also stop Powerdevil. Hope it helps.

Comment 3 slavo 2010-10-22 22:14:01 UTC

*** This bug has been confirmed by popular vote. ***

Comment 4 Dario Freddi 2010-11-09 17:28:29 UTC

This should be fixed in 4.6, where it is also possible for applications to require a suspension of screen power management features (hence presentation profile no longer applies)

Comment 5 Carlos Alberto Espinal 2012-03-01 11:42:35 UTC

This bug seems to be back in KDE 4.8. Can anyone confirm this?

Comment 6 vx 2012-03-24 15:50:17 UTC

I'm having the same issues in 4.8.1.

Comment 7 algspd 2013-05-10 21:56:07 UTC

Same problem in 4.8.4.
Workaround here: http://bit.ly/15x1yqP
:)