Red Hat Bugzilla – Full Text Bug Listing
|Summary:||Brightness issues with asus-laptop|
|Product:||[Fedora] Fedora||Reporter:||Christoph Wickert <cwickert>|
|Component:||gnome-power-manager||Assignee:||Richard Hughes <richard>|
|Status:||CLOSED CURRENTRELEASE||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Fixed In Version:||2.26.4-1.fc11||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2009-08-25 04:19:04 EDT||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
Description Christoph Wickert 2009-02-16 18:56:28 EST
Description of problem: The latest update of gnome-power-manager which was supposed to fix some brightness issues actually broke the brightness control on my Asus F3P. Version-Release number of selected component (if applicable): gnome-power-manager-2.24.4-1.fc10 How reproducible: always Steps to Reproduce: 1. $ gconftool-2 --get /apps/gnome-power-manager/backlight/brightness_ac 100 $ cat /proc/acpi/ac_adapter/AC0/state state: on-line $ cat /proc/acpi/video/VGA/LCDD/brightness levels: 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 current: 13 IMO g-p-m should set the brightness to 15 once it's started, but that's another issue. Until now this is the "normal" behavior that I have already seen with previous versions of g-p-m. 2. Try to increase brightness with Fn keys or the brightness applet. Actual results: Brightness cannot be increased. Both the applet as well as the popup show brightness already at 100%, although it is not. I first have to _de_crease it a little and then can increase it to full brightness again. Nevertheless /proc/acpi/video/VGA/LCDD/brightness does not change at all. Expected results: Brightness applet and popup should reflect the current state correctly. /proc/acpi/video/VGA/LCDD/brightness should change
Comment 1 Christoph Wickert 2009-03-07 15:31:54 EST
Things have become worse with kernel kernel-188.8.131.52-170.2.35.fc10.i686: /proc/acpi/video/VGA/LCDD/brightness always is at 0 and the display is so dark that I hardly can see anything and have to login blindly. Downgrading to gnome-power-manager-2.24.1-3.fc10.i386 fixes my problems. /proc/acpi/video/VGA/LCDD/brightness still does not change, but at least the display brightness is correct. Please tell me what you need to debug this problem. TIA.
Comment 2 Christoph Wickert 2009-03-19 15:21:08 EDT
(In reply to comment #1) > Downgrading to gnome-power-manager-2.24.1-3.fc10.i386 fixes my problems. No, not really. But I realized that the problem only appears when I'm on AC. When booting on battery, the brightness is set to the correct value. Nevertheless still no changes in /proc/acpi/video/VGA/LCDD/brightness.
Comment 3 Richard Hughes 2009-03-20 07:59:25 EDT
HAL doesn't use /proc/acpi/video/* anymore. Does this work correctly with XRANDR? This is how g-p-m by default tries to change the brightness, and falls back to HAL and the backlight class if this is not available. If you grab me a gnome-power-manager --verbose log i can start debugging this, although the problem looks deeper than g-p-m. Richard
Comment 4 Christoph Wickert 2009-03-29 11:18:43 EDT
(In reply to comment #3) > HAL doesn't use /proc/acpi/video/* anymore. But it can still be used, right? > Does this work correctly with XRANDR? How can I test this? man xrandr does not mention brightness. > This is how g-p-m by default tries to > change the brightness, and falls back to HAL and the backlight class if this is > not available. If you grab me a gnome-power-manager --verbose log i can start > debugging this, although the problem looks deeper than g-p-m. Any idea how to get a log of the g-p-m that is started in gdm? I tried editing /usr/share/gdm/autostart/LoginWindow/gnome-power-manager.desktop to "Exec=gnome-power-manager --verbose > /var/log/gdm/gnome-power-manager.log", but the log is never created, although gdm has the permissions to do so.
Comment 5 Christoph Wickert 2009-04-06 07:43:49 EDT
Created attachment 338320 [details] g-p-m log 3 x brightness up (no effect) 3 x brightness down (brightness increased in first key stroke) 3 x brightness up again (to full brightness)
Comment 6 Christoph Wickert 2009-05-31 11:02:06 EDT
I think I delivered the log you asked me for in comment # 3. Is there more you need to debug this problem?
Comment 7 Richard Hughes 2009-08-20 07:37:27 EDT
Does this still happen with F11?
Comment 8 Christoph Wickert 2009-08-25 04:19:04 EDT
Nope, seems to be fixed. Closing.