Bug 314810

Summary:	Dragonplayer turns on DPMS
Product:	[Frameworks and Libraries] solid	Reporter:	Zach <zachleigh>
Component:	powermanagement	Assignee:	Dario Freddi <drf>
Status:	RESOLVED NOT A BUG
Severity:	normal	CC:	myriam, oliver.henshaw
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:

Description Zach 2013-02-10 04:50:43 UTC

Playing a video in Dragonplayer durns DPMS on.  After Dragonplayer is colsed, this causes the screen to turn off after 10 minutes of activity.

Reproducible: Always

Steps to Reproduce:
1.  Turn off DPMS: xset -dpms  (Check to make sure its off: xset -q)
2.  Play a video for a few seconds with Dragonplayer and close the program
3.  Check xset again to find DPMS is now on: xset -q
Actual Results:  
DPMS is on

Expected Results:  
DPMS should be off

Comment 1 Oliver Henshaw 2013-02-10 16:08:26 UTC

(from https://bugs.kde.org/show_bug.cgi?id=295814#c21 )
> Upgraded to 4.10 and was still having issues.  Did some playing around and
> found that Dragonplayer turns DPMS on.  On startup, xset -q gives the proper
> output, but after playing a video in Dragonplayer...
> 
> DPMS (Energy Star):
>   Standby: 0    Suspend: 0    Off: 0
>   DPMS is Enabled
>   Monitor is On

This is fine - the zero timeouts means that DPMS is effectively off. Are you sure this is from after you closed dragonplayer?

But you shouldn't need to manually disable DPMS with xset, just configure powerdevil appropriately (assuming kde-workspace >= 4.9.3, as noted in the earlier bug).

Comment 2 Harald Sitter 2013-02-11 11:31:33 UTC

What Oliver said.

Moving to solid pm as this is not a problem in dragon.

Comment 3 Zach 2013-02-12 00:47:46 UTC

True, because of the zero timeouts DPMS doesnt actually turn on, but Dragonplayer should not be activiating DPMS.

Comment 4 Oliver Henshaw 2013-02-12 14:48:36 UTC

Enabling DPMS in some situations is something that can't be avoided (e.g. 'xset -dpms; xset -q; sleep 5; xset dpms force off' and 'xset -q' after you wake the screen and you'll see that dpms has been re-enabled)  - that's why we now set the timeouts to zero when dpms should be disabled. 

It's possible that the phonon backend is doing this, i.e. disabling and enabling dpms by itself. It's sub-optimal but harmless. I think that vlc 2.1 will perform better in this regard, i.e. using the freedesktop ScreenSaver inhibit interface.

So resolving as INVALID seems the best fit. Please re-open if I've misunderstood and there's a real problem here.