Bug 430474 - KDE4 display not turning off
Summary: KDE4 display not turning off
Status: RESOLVED DUPLICATE of bug 450254
Alias: None
Product: openSUSE 11.0
Classification: openSUSE
Component: KDE4 Workspace (show other bugs)
Version: Final
Hardware: x86-64 openSUSE 11.0
: P2 - High : Normal (vote)
Target Milestone: ---
Assignee: Lubos Lunak
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-28 09:52 UTC by Atri Bhattacharya
Modified: 2008-12-01 10:21 UTC (History)
0 users

See Also:
Found By: Customer
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 Atri Bhattacharya 2008-09-28 09:52:21 UTC 
KDE Version 4.1.2 (KDE 4.1.1 (KDE 4.1 >= 20080828)) "release 52.2" (OBS)
KDE4 does not lock (or even blank) screen even though the option to do so has been enabled (and set to x mins) in the Personal Settings. Further even if screen is locked from the main-menu or Ctrl+Alt+L monitor does not turn off though in the Personal Settings, Display Power Management settings are enabled (and set to x mins). NVIDIA Graphics card, and latest nvidia drivers (173.14.12) installed.
Comment 1 Atri Bhattacharya 2008-11-01 09:13:03 UTC 
Problems with screen-locking resolved (Version 4.1.2 (KDE 4.1.2) "release 49.1" and nVidia drivers 177.80), but monitor turning off still does not work even though enabled from display settings in KDE system-settings.
Comment 2 Atri Bhattacharya 2008-11-07 16:01:29 UTC 
Just update to 4.1.3 from Factory/Desktop repo, and monitor turning off still does not work. This problem exists with openSUSE 11.1 B4 too.
Comment 3 Atri Bhattacharya 2008-11-15 06:42:49 UTC 
Display turning off still not working with openSUSE 11.1 Beta5. Hopefully this will be fixed before final release, it is rather a pain to turn off the monitor manually every time.
Comment 4 Lubos Lunak 2008-12-01 10:21:55 UTC 

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