Bug 299979

Summary: Display dimmed twice within a few seconds
Product: [Frameworks and Libraries] solid Reporter: S. Burmeister <sven.burmeister>
Component: powermanagement-daemonAssignee: Dario Freddi <drf>
Status: RESOLVED DUPLICATE    
Severity: normal CC: oliver.henshaw
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:

Description S. Burmeister 2012-05-14 07:37:43 UTC
4.8.3: If my battery is low the display is dimmed ~20 seconds after I moved the mouse last. This should actually be one minute, but anyway.

debug shows:

kded(1714) PowerDevilUPowerBackend::brightness: Screen brightness:  100
kded(1714) PowerDevilUPowerBackend::brightness: Screen brightness:  100
kded(1714) PowerDevilUPowerBackend::setBrightness: set screen brightness:  50

Wrong timing, but ok. Yet a few seconds later the display is dimmed again.

kded(1714) PowerDevilUPowerBackend::brightness: Screen brightness:  57.1429
kded(1714) PowerDevilUPowerBackend::setBrightness: set screen brightness:  14.2857

powermanagementprofilesrc:

[AC]
icon=battery-charging

[AC][BrightnessControl]
value=100

[AC][DPMSControl]
idleTime=600

[AC][HandleButtonEvents]
lidAction=1
powerButtonAction=16

[Battery]
icon=battery-060

[Battery][BrightnessControl]
value=60

[Battery][DPMSControl]
idleTime=300

[Battery][DimDisplay]
idleTime=120000

[Battery][HandleButtonEvents]
lidAction=1
powerButtonAction=16

[Battery][SuspendSession]
idleTime=600000
suspendType=1

[LowBattery]
icon=battery-low

[LowBattery][BrightnessControl]
value=30

[LowBattery][DPMSControl]
idleTime=120

[LowBattery][DimDisplay]
idleTime=60000

[LowBattery][HandleButtonEvents]
lidAction=1
powerButtonAction=16

[LowBattery][SuspendSession]
idleTime=300000
suspendType=1


Reproducible: Always

Steps to Reproduce:
1. Use the above settings
2. Wait until the battery is low
3. Wait until the screen is dimmed
Actual Results:  
dimmed too early (yab)
dimmed twice

Expected Results:  
dim only once
Comment 1 Oliver Henshaw 2013-02-17 15:12:53 UTC

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