brightness settings not applied

Bug #413303 reported by myrtille
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-power-manager (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I'm using Kubuntu Jaunty with KDE 4.2.4 and mostly the 2.6.30 kernel on an acer travelmate 6492.

When I try to change the brightness of my desktop with either the FN-keys or the powermanager-widget or the systemsettings, I can change the settings but they have no effect on the brightness. I effectively can't change it, it is always set to maximal brightness.

I can change brightness just fine when I boot into the 2.6.28-14 kernel.

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 9.04
Release: 9.04
Codename: jaunty

kernel version of the 2.6.28:
2.6.28-14-generic

kernel version of the 2.6.30:
2.6.30-020630rc6-generic

Revision history for this message
myrtille (akm1984) wrote :

This is still true for Karmic and kernel 2.6.31-11. The brightness remains unchanged when I unplug or plug in the powersupply for my laptop.

Revision history for this message
myrtille (akm1984) wrote :

The bug is still present in kernel 2.6.31-16 karmic kubuntu used with kde 4.3.2.

If nobody reacts to this comment, I will consider this bug as stale and stop updating it. It has been 6 month since I originally posted the problem and nobody has reacted to it since then.
regards

Revision history for this message
myrtille (akm1984) wrote :

Final I have since reinstalled, switched to 64bit, grub2 and ext4 on my system and am currently running kernel 2.6.31-21-generic and kde 4.4.2

brightness settings still can't be changed.

Revision history for this message
Fabio Marconi (fabiomarconi) 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.

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://help.ubuntu.com/community/ReportingBugs.

affects: ubuntu → gnome-power-manager (Ubuntu)
Changed in gnome-power-manager (Ubuntu):
status: New → Incomplete
Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

Hello myrtille
Are you experiencing this issue with the latest updated Lucid's packages ?
Thanks in advance
:)Fabio

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in gnome-power-manager (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
myrtille (akm1984) wrote :

Finally fixed with an upgrade to kernel 2.6.35-24-generic last week.

I must have missed your request in august and i didn't check back as the situation continued unchanged.

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.