sets wrong brightness value with xrandr
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
hal-info (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: gnome-power-manager
My laptop display backlight has 16 brightness values (0-15). If gnome-power-manager is not running and I set it all the way down to 0 (via fn-brightness-down) and watch /sys/class/
If gnome-power-manager is running, I see the values 0, 2, 4, 6, 8, ..., 14, 15, i.e. jumping two levels up each time I increase the brightness one step. The backlight however really only increases the level by one each time I press fn-brightness-up, so when actual_brightness reaches 15 the actual brightness I see on my display is around half of the full backlight level.
This causes the brightness notifications from notify-osd to report bogus values (thinking I already reached maximum when I'm just on half brightness etc.)
This behaviour started very recently, probably when the xrandr-backlight KMS capability was enabled, it was working fine before.
I'm not sure whether this is actually the fault of xserver-
Attaching the output of gnome-power-manager --verbose when incrementally setting the brightness from zero to full.
ProblemType: Bug
Architecture: amd64
Date: Sat Oct 17 09:41:01 2009
DistroRelease: Ubuntu 9.10
Package: gnome-power-manager 2.28.0-0ubuntu7
ProcEnviron:
PATH=(custom, user)
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: gnome-power-manager
Uname: Linux 2.6.31-14-generic x86_64
XsessionErrors:
(gnome-
(gnome-
(polkit-
(nautilus:2646): Eel-CRITICAL **: eel_preferences
(Do:2666): Wnck-CRITICAL **: wnck_set_
The behavior has changed: Pressing fn-brightness- up/down while gnome-power-manager is running still causes actual_brightness to jump up/down two levels on each keypress, but it now represents the correct brightness (i.e. my display backlight really increases or decreases its brightness by two levels). manager. BIOS (or hardware directly, however this is actually implemented) reacts to fn-brightness-up by increasing the brightness one level. g-p-m also reacts to the keypress by increasing the brightness by one level. This causes the backlight to actually increase its brightness twice on a single keypress.
I believe that the keypress is both handled by my laptop directly and by gnome-power-
lshal reports for my backlight:
udi = '/org/freedeskt op/Hal/ devices/ computer_ backlight' addon-generic- backlight' } (string list) op.Hal. Device. LaptopPanel' } (string list) op/Hal/ devices/ computer' (string) op/Hal/ devices/ computer_ backlight' (string) panel.access_ method = 'general' (string) panel.brightnes s_in_hardware = false (bool) panel.num_ levels = 16 (0x10) (int) hotplug_ type = 2 (0x2) (int) virtual/ backlight/ acpi_video0' (string)
info.addons = {'hald-
info.capabilities = {'laptop_panel'} (string list)
info.category = 'laptop_panel' (string)
info.interfaces = {'org.freedeskt
info.parent = '/org/freedeskt
info.product = 'Generic Backlight Device' (string)
info.subsystem = 'backlight' (string)
info.udi = '/org/freedeskt
laptop_
laptop_
laptop_
linux.
linux.subsystem = 'backlight' (string)
linux.sysfs_path = '/sys/devices/
laptop_ panel.brightnes s_in_hardware being set to false is wrong, my laptop supports that.