Bug 182735 - powerdevil & initial screen brightness
Summary: powerdevil & initial screen brightness
Status: RESOLVED FIXED
Alias: None
Product: solid
Classification: Unmaintained
Component: powermanagement-daemon (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Dario Freddi
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-01 16:01 UTC by Harald Nikolisin
Modified: 2010-11-09 20:29 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Harald Nikolisin 2009-02-01 16:01:04 UTC
Version:            (using KDE 4.2.0)
OS:                Linux
Installed from:    SuSE RPMs

There is a small error relating the powerdevil settings in KDE 4.2

I set up 2 profiles, like my_performance & my_powersaving.

Then I assign 2 screen brightnesses to the profiles. I tested it on the fly through dis- and reconnecting the cable - it works.

The error is that when I starting the computer in my_powersaving mode (through disconnection the cable) - the initial screen brightness was not applied.

However if I connect the cable, and immediately disconnect the cable, then It applies the new screen brightness. 
Therefore it's only a initialising problem. Please apply the inital screen brightness.
Comment 1 Dario Freddi 2009-02-07 13:39:24 UTC
I can't reproduce it here. Every setting is applied on startup, including brightness. Can you please investigate this further? For example, please have a look at kded4 startup messages.
Comment 2 Harald Nikolisin 2009-02-08 03:45:38 UTC
Sorry, wrong assumption.

Screen Brightness control does not work at all with powerdevil. The jumps when disconnecting the power cable were introduced by pommed service which links the special keys of a MacBook (Pro) to the underlying system.

But only stopping the pommed service does not lead to a working screen brightness control of powerdevil.
Maybe pommed does use another path to access the hardware information. Even if you cannot fix this problem easily, can you provide some background infos here?

In general there arises a integration problem of pommed and powerdevil. Should I open another bug entry for this topic?
Additionaly DPMS control does not work. Should I also open a new bug for that, or should I open a bug only related for the topic "powerdevil on MacBook (Pro) Hardware"?

Comment 3 Marc Benstein 2009-02-12 17:29:50 UTC
This has also been reported downstream here: https://bugzilla.novell.com/467779

powerdevil's brightness slider does not change when I change profiles (manually
or automatically). The monitor brightness does however change as desired.
Manually adjusting the slider is also successful.



Reproducible: Always

Steps to Reproduce:
1. remove ac power to laptop
2. powersave profile turns on, brightness is dimmed
3. open powerdevil, brightness bar is at 100%]
Comment 4 Dario Freddi 2010-11-09 20:29:40 UTC
This has been already fixed time ago