Brightness settings stopped working after upgrade

[krishnan sampath]

I upgraded from saucy to trusty on my lenovo g505s laptop. After the upgrade, both the physical key and the brightness settings in the gnome-control centre have stopped working. Whatever level of brightness i decrease it to, it always stays on maximum.
I'm able to reproduce this only on kernel 3.13. Works as its supposed to on kernel 3.12

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: gnome-control-center 1:3.6.3-0ubuntu50
ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7
Uname: Linux 3.13.0-2-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.13.1-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Jan 12 09:17:00 2014
ExecutablePath: /usr/bin/gnome-control-center.real
InstallationDate: Installed on 2013-11-16 (56 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to trusty on 2014-01-06 (5 days ago)
---
ApportVersion: 2.13.1-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: krishnan 3070 F.... pulseaudio
 /dev/snd/controlC0: krishnan 3070 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=c545b9da-fef4-4530-9051-29276dfd842c
InstallationDate: Installed on 2013-11-16 (58 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: LENOVO INVALID
NonfreeKernelModules: fglrx
Package: linux (not installed)
ProcFB: 0 simple
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-2-generic root=UUID=0b897d24-0c02-4f57-9596-5fcd681c5ed0 ro quiet splash nomodeset vt.handoff=7
ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-2-generic N/A
 linux-backports-modules-3.13.0-2-generic N/A
 linux-firmware 1.121
StagingDrivers: rts5139
Tags: trusty staging
Uname: Linux 3.13.0-2-generic x86_64
UpgradeStatus: Upgraded to trusty on 2014-01-06 (6 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 04/23/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: 83CN12WW(V1.01)
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Lenovo G505s
dmi.board.vendor: LENOVO
dmi.board.version: 00000000Not Defined
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo G505s
dmi.modalias: dmi:bvnLENOVO:bvr83CN12WW(V1.01):bd04/23/2013:svnLENOVO:pnINVALID:pvrLenovoG505s:rvnLENOVO:rnLenovoG505s:rvr00000000NotDefined:cvnLENOVO:ct10:cvrLenovoG505s:
dmi.product.name: INVALID
dmi.product.version: Lenovo G505s
dmi.sys.vendor: LENOVO

[Sebastien Bacher (seb128)]

Thanks

"reproduce this only on kernel 3.13. Works as its supposed to on kernel 3.12" -> that's a kernel issue

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1268252

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[krishnan sampath (tskrishnan)]

apport information

[krishnan sampath (tskrishnan)]

apport information

[krishnan sampath (tskrishnan)]

apport information

[krishnan sampath (tskrishnan)]

apport information

[krishnan sampath (tskrishnan)]

apport information

[krishnan sampath (tskrishnan)]

apport information

[krishnan sampath (tskrishnan)]

apport information

[krishnan sampath (tskrishnan)]

apport information

[krishnan sampath (tskrishnan)]

apport information

[krishnan sampath (tskrishnan)]

apport information

[krishnan sampath (tskrishnan)]

apport information

[krishnan sampath (tskrishnan)]

apport information

[krishnan sampath (tskrishnan)]

apport information

[krishnan sampath (tskrishnan)]

apport information

[krishnan sampath (tskrishnan)]

apport information

[krishnan sampath (tskrishnan)]

apport information

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.13 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-rc8-trusty/

[krishnan sampath (tskrishnan)]

tested with mainstraem kernel. problem exists there too. I also noticed that if i use the physical button to change the brightness, wifi stops working immediately. Is it somehow related or should i open another bug report for that too?

[Rüdiger Kupper (ruediger.kupper)]

Confirmed on a Thinkpad T61 after upgrade to Trusty.
Possible duplicate: Bug 1280927

[Simon Wenner (nowic)]

I can confirm this bug on a HP Mini 5103 (Ubuntu 14.04, 32bit).

[Joseph Salisbury (jsalisbury)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

  With the recent release of this Ubuntu release, would like to confirm if this bug is still present. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.