Bug 201235 - powerdevil asks to configure timeouts for dpms states not supported by monitor
Summary: powerdevil asks to configure timeouts for dpms states not supported by monitor
Status: RESOLVED FIXED
Alias: None
Product: solid
Classification: Frameworks and Libraries
Component: powermanagement-kcm (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Dario Freddi
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-23 15:43 UTC by Oliver Henshaw
Modified: 2010-11-09 17:16 UTC (History)
0 users

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 Oliver Henshaw 2009-07-23 15:43:57 UTC
Version:            (using KDE 4.2.4)
OS:                Linux
Installed from:    Fedora RPMs

In System Settings -> Power Management -> Edit Profiles -> Screen I can configure timeouts for "Standby after", "Suspend after", "Power off after". But according to my Xorg.0.log, standby and suspend are not supported by this monitor:

$ grep -i dpms /var/log/Xorg.0.log                  
(II) Loading extension DPMS
(II) RADEON(0): DPMS capabilities: Off; RGB/Color Display
(II) RADEON(0): DPMS enabled
(II) RADEON(0): DPMS capabilities: Off; RGB/Color Display

Powerdevil should only allow me to change the settings that make sense for my monitor.


Affected packages:
kdebase-workspace-4.2.4-5.fc11.i586
Comment 1 Oliver Henshaw 2009-08-26 19:18:52 UTC
This is unchanged in kdebase-workspace-4.3.0-9.fc11.i586

I assume Xorg is reporting accurately? In any case, the monitor never enters any kind of power-saving mode on idle.
Comment 2 Dario Freddi 2009-12-01 18:40:34 UTC
Uhm, actually I'm grabbing the capability from XOrg, I'll see if I can improve that
Comment 3 Oliver Henshaw 2010-10-07 23:58:58 UTC
What's actually happening is that the monitor's EDID reports that it only supports the DPMS Off state. However any of the DPMS states can be forced with xset, so I don't know whether the EDID is wrong or what.
Comment 4 Dario Freddi 2010-11-09 17:16:32 UTC
Should be fixed in 4.6