Bug 485845
Summary: | Brightness issues with asus-laptop | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Christoph Wickert <christoph.wickert> | ||||
Component: | gnome-power-manager | Assignee: | Richard Hughes <richard> | ||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | low | ||||||
Version: | 10 | CC: | rhughes, richard | ||||
Target Milestone: | --- | Keywords: | Regression | ||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | 2.26.4-1.fc11 | Doc Type: | Bug Fix | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2009-08-25 08:19:04 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Christoph Wickert
2009-02-16 23:56:28 UTC
Things have become worse with kernel kernel-2.6.27.19-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. (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. 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 (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. 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)
I think I delivered the log you asked me for in comment # 3. Is there more you need to debug this problem? Does this still happen with F11? Nope, seems to be fixed. Closing. |