laptop brightness keys regression

[Seth Arnold]

In 12.04 LTS and 12.10, the fn+f8 and fn+f9 keys properly adjusted my Thinkpad T530's display brightness perfectly.

I upgraded to Raring on Mar 17, and the brightness keys no longer work. The indicator appears but the slider does not slide and the screen brightness does not change.

The brightness slider on the brightness and lock control panel feels like it has lost granularity -- but I cannot recall the exact behavior of the older slider.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[chrisle (chrisle)]

same problem here on lenovo thinkpad l430

[Seth Arnold (seth-arnold)]

On Fri 5 April 2013, the brightness keys _almost_ work -- if the "Brightness" slider in the System Settings | Brightness & Lock is moved to roughly 2/3 of the brightness, the keyboard brightness keys can control _some_ of the brightness. It is still not as granular as 12.04 LTS or 12.10, and full brightness and full dimness are impossible, but I finally have some amount of keyboard control over brightness again.

Did I make a mistake when I assigned this bug to gnome-control-center? I'm a bit surprised that no one has asked for logs or edid info or anything else about my system to try to debug this regression.

Thanks

[jerrylamos (jerrylamos)]

Acer Aspire 5253 15" notebook, variation of the brightness problem:

Used to be, ubuntu would remember the brightness setting when booting again.

Raring unity ubuntu always sets MAX BRIGHT on every boot so I have to do system settings > brightness every time.

How come Raring doesn't remember the brightness setting?

[Seth Arnold (seth-arnold)]

Well, the brightness on my machine seems to be set to too-bright at boot, before Unity enters the picture. But not knowing what to reset it to, and busted keys, that might well be Unity's fault.

I'm unassigning the package in the hopes that by doing so it will enter a different triage queue and maybe get more traction. (We really can't release Raring like this..)

I also changed the title to reflect that it isn't just my specific model.

Thanks Jerry

[Seth Arnold (seth-arnold)]

@Jerry, the bug I dup'd to has a lot of mentions of Lenovo -- your Acer may have made the same mistake our Lenovos did, but it might have made a different mistake. Or maybe it's the usual "Unity forgets some settings at reboot". You might want to report a new bug...

[penalvch (penalvch)]

Seth Arnold, 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 (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. 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:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.13-rc3

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:
needs-upstream-testing

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

As well, please remove the tag:
needs-upstream-testing

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.

[Seth Arnold (seth-arnold)]

Christopher, why did your scripts inspect this bug? It was marked as a duplicate of another bug and I cannot see any good reason for removing the duplicate status. I am putting the duplicate back, so that this bug falls off the visibility again, and the stronger bug wins.

Please inspect your scripts, I believe they are incorrect.

Thanks.

[penalvch (penalvch)]

Seth Arnold, it's not a script. ;) There is no hardware information to inspect for this report. So, it would be helpful if you provided the information previously requested.

Thank you for your understanding.

[Seth Arnold (seth-arnold)]

It's not a script? How did you even find this bug? :)

The raring SRU completed successfully, and saucy (which I'm running now) didn't exhibit this problem thanks to the bughunting done before the raring SRU. As far as I'm concerned this is handled...

Thanks