[gutsy tribe 4] brightness keys no longer work but system automagically updates to full brightness after 60 seconds

Bug #131338 reported by Christer Edwards
6
Affects Status Importance Assigned to Milestone
gnome-power-manager (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: 915resolution

My guess is this is related to the 915resolution package, or that of the updated kernel. In Feisty the brightness hardware keys (fn-f1 & fn-f2) worked fine for adjusting the screen brightness. Now, recently noticed in tribe 4 release they do not.

Turning up the brightness effectively brings it to the lowest setting and won't re-adjust to a higher value (although the meter is displayed on the screen as usual).

However, if I leave the machine idle for 60 seconds the brightness will auto-readjust itself to its previous full brightness level.

Revision history for this message
unggnu (unggnu) wrote :

Could you please recheck it with Gutsy Final or maybe the Live CD? If it doesn't work please attach the files '/etc/X11/xorg.conf', '/var/log/Xorg.0.log', the output of "lspci -vvnn" and post the output of "lspci -nn | grep VGA".

Changed in 915resolution:
status: New → Incomplete
Revision history for this message
Russel Winder (russel) wrote : Re: Gutsy brightness keys brightness work but system automagically updates to full brightness

Not sure if this is the same thing but...

I have just upgraded my AJP M3000N (which is a rebadged ASUS M3000N) from Feisty to Gutsy. The brightness keys (Fn-F5 and Fn-F6) work fine in Gutsy just as they did in Feisty. However, after a short period, the brightness is reset to full, which is extremely annoying, especially when working in low-light conditions. NB That is REALLY annoying!

I have tried it with the brightness applet on the panel and without the brightness applet on the panel and it definitely appears to make no difference, after a period of time, brightness is reset to full on. However, I will keep experimenting to see what stops this new, and wrong behaviour in Gutsy. Feisty didn't do this, it worked exactly as I wanted it to.

My current hypothesis is that the rest occurs if the keys are used but not if the applet is used to set the brightness.

PS I am using 855resolution not 915resolution to set the 1400x1050 screen size on this machine.

Revision history for this message
Russel Winder (russel) wrote : Re: Gutsy brightness keys work but system automagically updates to full brightness set by applet

It seems that using the keys to set the brightness leads to a temporary change of brightness. There is some time out that then resets the brightness to the level determined by the applet on the panel. I would suggest this is an error not a feature. Is it deserving a new bug number or does this one cover it?

unggnu (unggnu)
Changed in 915resolution:
status: Incomplete → New
Revision history for this message
Christer Edwards (christer.edwards) wrote :

I no longer have this issue. If no one else still has this problem I'll close the bug.

Revision history for this message
Russel Winder (russel) wrote :

On my AJP M3000N I still have the problem. The brightness applet sets the brightness permanently whereas using the keys causes the brightness to change and then about 60s later to revert to the setting of the applet. When the keys are being used a brightness indicator appears on the screen. Basically there appear to be two independent brightness changing mechanisms of which the applet takes some form of precedence on a refresh timer.

On my Sony Vaio PCG-SRX51P/B the brightness applet has no effect whatsoever on the screen brightness, the keys work fine and have permanent effect.

Both machines are running 7.10 Gutsy release with all updates applied.

On the AJP M300N I used to have to run 855resolution package to get the 1400x1050 resolution. I am now using the Intel driver so that resolution works properly without the intervention of 855resolution (or 915resolution) -- neither package is installed on the machine. Even xrandr works as expected :-) but the brightness controls do not.

Revision history for this message
Russel Winder (russel) wrote :
Revision history for this message
Russel Winder (russel) wrote :
Revision history for this message
Russel Winder (russel) wrote :
Revision history for this message
Russel Winder (russel) wrote :
Revision history for this message
Russel Winder (russel) wrote :

The above files are from the AJP M3000N. I hope they are what was asked for.

Revision history for this message
Daniel T Chen (crimsun) wrote :

Is this symptom still reproducible in 8.10?

Changed in acpi-support:
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) 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:
status: Incomplete → Invalid
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.