gnome-brightness-applet fails to change brightness
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: gnome-power-manager
I am using ubuntu-bug in Intrepid beta (upgraded to most recent). I hope all the deep details are being automatically reported. ubuntu-bug was called right after the applet failed to change the brightness after the slider had been moved.
I want to append this report to Bug #222171, "[Hardy] Backlight low on Asus x57 laptop (M50sa)" as a response to a request by https:/
The Intrepid install is into an Asus M70vm. This machine has a light sensor, as do all of the machines reported in Bug #222171, I believe.
Here's my take on the problem. The kernel driver that controls the backlight has two variables in /sys/devices/
The gnome applet gives two error conditions upon attempts to set the brightness
1) unable to read the brightness (no exact words)
2) cannot connect to gnome-power-manager
This asus comes with their "express gate" OS, which I understand is Gnu/Linux. In "express gate", the light sensor is overriden, and all FN keys work. I wonder why their driver has not been contributed back to Gnu/Linux, and why there is no information offered as to how to find information about either their driver or hardware information.
My crude workaround is to chmod go+w at end of boot, because the files in /sys/devices/
ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/lib/
NonfreeKernelMo
Package: gnome-power-manager 2.24.0-0ubuntu4
ProcEnviron:
LANG=en_US.UTF-8
PATH=/
SHELL=/bin/bash
SourcePackage: gnome-power-manager
Uname: Linux 2.6.27-7-generic x86_64
t_e_r, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http:// cdimage. ubuntu. com/daily- live/current/ .
If it remains an issue, could you please run the following command in the development release from a Terminal (Applications- >Accessories- >Terminal) , as it will automatically gather and attach updated debug information to this report:
apport-collect -p linux <replace- with-bug- number>
Also, could you please test the latest upstream kernel available following https:/ /wiki.ubuntu. com/KernelMainl ineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags: fixed-upstream fixed-upstream- VERSION- NUMBER
kernel-
kernel-
where VERSION-NUMBER is the version number of the kernel you tested. For example: fixed-upstream- v3.11
kernel-
This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag: testing
needs-upstream-
If the mainline kernel does not fix this bug, please add the following tags: bug-exists- upstream bug-exists- upstream- VERSION- NUMBER
kernel-
kernel-
As well, please remove the tag: testing
needs-upstream-
Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.