Bug 264983 - randomly changing brightness settings of display
Summary: randomly changing brightness settings of display
Status: RESOLVED FIXED
Alias: None
Product: solid
Classification: Frameworks and Libraries
Component: powermanagement (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Dario Freddi
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-31 18:45 UTC by michael
Modified: 2011-05-10 14:02 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description michael 2011-01-31 18:45:18 UTC 
Version:           unspecified (using KDE 4.6.0) 
OS:                Linux

Since the update from 4.5.5 to 4.6 I have problems with the brightness settings of the display. The display brightness switches without any interaction randomly but constantly to different values. It appears only after the first resume cycle.

Reproducible: Always

Steps to Reproduce:
Start KDE and make one suspend and resume cycle.



I am using a Lenovo T61p and use the latest NVIDIA-264-driver, which works so far perfectly with KDE 4.5.5.
Comment 1 michael 2011-01-31 19:31:03 UTC 
Going back to the latest OpenSuSE-KDE-4.5.5 it works as it should be, with
no switching of brightness levels.
Comment 2 Martin Steigerwald 2011-05-10 11:56:59 UTC 
Some questions:

- do you have a power profile selected? I had none selected after upgrade to new reduced standard set of power profiles

- I suggest you to go to power management kcm in systemsettings and reset the profiles to their new default values

- The new "performance" profile has a brightness darkening timeout. If you do not want darkening the display after a timeout, then disable this

Additionally

Bug 272917 -  leaves session darkened after switching to it after darkening timeout has expired

might be related: Do you work with several KDE sessions at once?
Comment 3 michael 2011-05-10 12:11:46 UTC 
OK, after updating to latest KDE-4.6.3 everything works as it should!

You can close the bug!

Thanks,

 Michael