Oh yeah! #24 is really dirty one! But it gave me a clue, how this bug should be fixed: Patching StepUp/StepDown handlers is very bad practice, because these methods may be called by some other applications. We need to prevent calls to these methods depending on some parameter.
The problem itself: bios changes brightness on keypress and reports acpi keypress event, instead of just reporting event (this might be fixable in DSDT), then some process handles this event and issues dbus calls to org.gnome.SettingsDaemon.Power.Screen.StepUp/StepDown methods. Then g-p-m changes brightness too; g-p-m has no ways to determine, whether it should change brightness when handling StepUp/StepDown dbus calls, or not. Neither 'some process' do. The solution, how I see it: find code, which handles acpi keypresses (that's not g-p-m, g-s-d may be?) and add user-changeable option there to disable acpi brightness keypresses handle (e.g. gconf parameter). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/527157 Title: Brightness controls skips Levels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/527157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
