It seems like what should happen when a user increases (or reduces) his brightness level beyond what is stored in /apps/gnome-power- manager/backlight/brightness_battery is that gnome-power-manager should store this new brightness value separately. When the computer becomes idle and g-p-m kicks in and dims the display, and then pops out of idle, g-p-m should reference this stored value instead of /apps/gnome-power- manager/backlight/brightness_battery to know what to set the brightness to. It's confusing to the end user to set the brightness to a certain level and then when they come out of idle for the computer to be set to a totally different level.
I've even hacked together a workaround for myself in the mean time. When the video_brightnessup/down scripts are called while on battery power, they grab the current brightness level and then change /apps/gnome- power-manager/backlight/brightness_battery to reflect that value. When it goes back to AC power, /apps/gnome-power- manager/backlight/brightness_battery is changed back to my preferred default value. This works, but is hacky and it would be much better if g-p-m simply stored the current pre-idle backlight value itself separately from /apps/gnome-power-manager/backlight/brightness_battery Just my two cents... -- Backlight no longer under my control on battery https://bugs.launchpad.net/bugs/131885 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
