Bug 434603 - Disply Power Control are not working.
Summary: Disply Power Control are not working.
Status: RESOLVED DUPLICATE of bug 462854
Alias: None
Product: openSUSE 11.1
Classification: openSUSE
Component: KDE4 Applications (show other bugs)
Version: Beta 2
Hardware: x86 Other
: P5 - None : Normal with 1 vote (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-12 15:09 UTC by Forgotten User tfBQIqYkT6
Modified: 2009-01-07 16:38 UTC (History)
2 users (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Forgotten User tfBQIqYkT6 2008-10-12 15:09:53 UTC 
Disply Power Control cannot be work in my system.Just have the screen saver running all day.OpenSUSE-11.1-Beta2-DVD-i386.iso KDE4 Environment.
Comment 1 Will Stephenson 2008-11-25 17:17:12 UTC 
Please try again with beta5 or newer.  These have a new power management applet, Powerdevil, that can set display power management.
Comment 2 nicholas tung 2009-01-02 05:10:25 UTC 
I'm using the released version (11.1) and updated all packages yesterday. The display does not seem to activate DPMS and power down on my laptop when I close the lid. The personal settings box says to use powerdevil, and I have it set to lock the display when the lid closes. I have the screen saver set to blank, which seems to be working. I'm working on a Latitude D420.

regards,
Nicholas
Comment 3 Forgotten User xkk2zRi74d 2009-01-05 13:59:10 UTC 
I have tried both Powerdevil and KPowerSave without any luck.

The only solution this far for me is to disable any screensaver. Only then the screen will be turned off.

Running 11.1 with KDE 4.1 and latest Nvida beta dirvers. Have tried latest stable Nvidia drivers with the same result.

/Anders
Comment 4 Lubos Lunak 2009-01-07 16:38:04 UTC 

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