touching the display brightness

[Thomas Schwinge]

The gnome-power-manager should have something like a check-box to disable the ``Set display brightness to'' slider and it should be disabled by default, i.e. g-p-m should not touch the display brichtness by default. And it definitely should not set it to 100% by default! (That probably is unhealthy for your eyes for nearly all of today's notebooks, at least if you're not working in a very lightish environment, and it's a waste of energy.)

It's very annoying if g-p-m modifies the display brightness every now and then, especially if you use your notebook (IBM/Lenovo T42 for me) during the day and during the night, and thusly there is no display brightness setting that fits both cases. I nearly always have to adjust the display brightness after g-p-m touched it, as there is no common denominator: having it at 100% during the night is nearly enough to enlighten the whole room, 50% is fine there, however 50% is not enough during the day.

That's why I propose for g-p-m not to touch that setting by default.

This applies to both of the ``Running on AC'' and ``Running on Battery'' cases.

I'm using the current Ubuntu Dapper, gnome-power-manager-2.13.93-0ubuntu3.

[Paul Sladen (sladen)]

This is related: #34897

[Paul Sladen (sladen)]

This is related:

  http://launchpad.net/bugs/34897

[Richard Hughes (richard-hughes)]

>g-p-m should not touch the display brichtness by default.

Whats the rationale? This stuff should "just work" rather than having to fiddle in the preferences enabling it.

>having it at 100% during the night is nearly enough to enlighten the whole room, 50% is fine there, however 50% is not enough during the day.

Do you have a brightness sensor on your laptop?

Richard.

[Thomas Schwinge (tschwinge)]

> >g-p-m should not touch the display brichtness by default.
>
> Whats the rationale? This stuff should "just work" rather than having to
> fiddle in the preferences enabling it.

Ok, then let's put it into different words: g-p-m has its private view of
the notebook's display brightness, which doesn't conform to the actual
state anymore as soon as I use the Fn-Home or Fn-End keys to modify it,
as Paul Sladen also pointed out in <URL:http://launchpad.net/bugs/34897>.
That's why we get the jumps on the display brightness as soon as g-p-m
gets active when resuming from hibernation, suspension or just the
screensaver.

So, g-p-m needs to be made aware of the actions on the display's
brightness that are happening outside of its scope by the user using the
Fn-Home or Fn-End key combinations.

Does that sound better?

(The same probably applies to the mixer application and the volume-up,
volume-down and mute keys.)

> >having it at 100% during the night is nearly enough to enlighten the
> whole room, 50% is fine there, however 50% is not enough during the day.
>
> Do you have a brightness sensor on your laptop?

No, I don't. At least I'm not aware of having one. ;-)

Do you want to pick up the ``not set [the display brightness] to 100% by
default'' issue?

[Richard Hughes (richard-hughes)]

>So, g-p-m needs to be made aware of the actions on the
>display's brightness that are happening outside of its
> scope by the user using the Fn-Home or Fn-End key
>combinations.

Valid point. Can you open a bug in http://bugzilla.gnome.org/enter_bug.cgi?product=gnome-power-manager and the upstream developers can discuss there. Please reference this bug in the new entry. Thanks.

[Thomas Schwinge (tschwinge)]

> Can you open a bug in
> http://bugzilla.gnome.org/enter_bug.cgi?product=gnome-power-manager and
> the upstream developers can discuss there. Please reference this bug in
> the new entry. Thanks.

Daniel Silverstone beat me to it and reported this issue here:
http://bugzilla.gnome.org//show_bug.cgi?id=335673

Thanks, Daniel!

[Matt Zimmerman (mdz)]

Surely either this or bug #34897 is a duplicate?

[Angelo Lisco (angystardust-gmail)]

This is related:
http://launchpad.net/bugs/35223