screen brightness control stopped working with 2.6.27-11

Bug #315255 reported by frapell
10
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

I updated Intrepid kernel to 2.6.27-11 and the brightness adjusting feature stopped working.
I tried cat /proc/acpi/video/VGA/LCD/brightness and i got <not supported>
now i'm using 2.6.27-10 and the feature works again and when i do cat /proc/acpi/video/VGA/LCD/brightness i get:
levels: 100 60 20 28 36 44 52 60 68 76 84 92 100
current: 100

both kernels are "generic"

laptop is an HP DV 2840 SE

regards

Revision history for this message
Lupine (thelupine) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in gnome-power-manager.

For future reference you might be interested to know that a lot of applications have bug reporting functionality built in to them. This can be accessed via the Report a Problem option in the Help menu for the application with which you are having an issue. You can learn more about this feature at https://wiki.ubuntu.com/ReportingBugs.

Also, I've been unable to reproduce your issue on Ubuntu 8.10. Can you reproduce this issue with an Ubuntu LIVE CD and report back if the problem still exists on Ubuntu 8.10 LIVE CD?

Revision history for this message
frapell (frapell) wrote :

mmmhh... i think this is a problem related to the kernel and not to "gnome-power-manager" as:
1) i do not use it, i'm using Kubuntu 8.10 (KDE 4.2)
2) the problem appeared when i upgraded my kernel version to 2.6.27-11, with 2.6.27-10 works fine

I will try to download a fresh new kubuntu live cd and try what you're suggesting.

Regards

Revision history for this message
Scott G (scotta-g1967) wrote :

I have the same issue after the update to 2.6.27-11 Kernel. If I boot into 2.6.27-9 all is well, if I then boot into 2.6.27-11 no brightness control. Works perfectly well with older kernel, just not the new proposed update.

I am running an Acer Aspire 5920G so not HP specific either

Revision history for this message
sasha (sasha123-deactivatedaccount) wrote :

The same problem for me. Screen brightness control stopped working after upgrade to 2.6.27-11. I am running an HP Pavilion dv6000 series laptop.

Revision history for this message
Lupine (thelupine) wrote :

Since it works with older kernel, and from the additional information you provided changing package to linux.

Revision history for this message
Lupine (thelupine) wrote :

Seem this is an old bug that has cropped back up again, marking as duplicate of:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/115525

Revision history for this message
Scott G (scotta-g1967) wrote :

I have one difference from the bug reported https://bugs.launchpad.net/ubuntu/+source/linux/+bug/115525

I still have control using Hardware Function keys to control the brightness

Revision history for this message
penalvch (penalvch) wrote :

frapell, thank you for reporting this and helping make Ubuntu better. Intrepid reached EOL on April 30, 2010.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If so, could you please test for this with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

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/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in 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 and remove the tag:
needs-upstream-testing

This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the text:
needs-upstream-testing

If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

Please let us know your results. Thank you for your understanding.

Helpful Bug Reporting Tips:
https://help.ubuntu.com/community/ReportingBugs

tags: added: intrepid needs-kernel-logs needs-upstream-testing regression-update
Changed in linux (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.