[xorg-edgers] Libnotify/brightness settings no longer displays/change with fn keys

[Sos Oganessian]

Prior to installing the xorg-edgers ppa, as well as during earlier versions from the ppa, the brightness settings panel/OSD would recognize and display any brightness settings changes that were initiated by the fn-keys of my Thinkpad Edge E220s. This has recently stopped. While the keys do still changes the brightness (and in fact they do some more smoothly), the settings/OSD do not reflect these changes. I'm not sure of the exact package causing the issue, so I've picked the generic “xorg”.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: xorg 1:7.6+12ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-3.3-generic 3.5.0-rc5
Uname: Linux 3.5.0-3-generic i686
.tmp.unity.support.test.0:

ApportVersion: 2.0.1-0ubuntu10
Architecture: i386
CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,ezoom,unityshell,scale,expo]
CompositorRunning: compiz
Date: Mon Jul 2 23:50:56 2012
DistUpgraded: Fresh install
DistroCodename: precise
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, even including gdb or git bisection work if needed
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:21e4]
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
Lsusb:
 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 003: ID 064e:c219 Suyin Corp.
MachineType: LENOVO 50382NU
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-3-generic root=UUID=f7b02149-e37d-4c34-8c52-167e92044b30 ro quiet splash i915.i915_enable_fbc=1 i915.lvds_downclock=1 drm.vblankoffdelay=1 elevator=noop vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/15/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: 8JET41WW (1.35 )
dmi.board.asset.tag: Not Available
dmi.board.name: 50382NU
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr8JET41WW(1.35):bd02/15/2012:svnLENOVO:pn50382NU:pvrThinkPadEdgeE220s:rvnLENOVO:rn50382NU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 50382NU
dmi.product.version: ThinkPad Edge E220s
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.7.8-0ubuntu1.1
version.libdrm2: libdrm2 2.4.36+git20120628.a7805194-0ubuntu0sarvatt~precise
version.libgl1-mesa-dri: libgl1-mesa-dri 8.1~git20120529.f92b2e5e-0ubuntu0sarvatt~precise
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 8.1~git20120529.f92b2e5e-0ubuntu0sarvatt~precise
version.xserver-xorg-core: xserver-xorg-core 2:1.12.2.901+git20120629+server-1.12-branch.b0be2d29-0ubuntu0ricotz~precise
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0+git20120504.f28507e8-0ubuntu0sarvatt~precise
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99+git20120628.179b0358-0ubuntu0sarvatt~precise
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.19.0+git20120702.e80f9c46-0ubuntu0sarvatt~precise
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.1+git20120702.0d2b414a-0ubuntu0sarvatt~precise

[Sos Oganessian (sos-u)]

Just recieved some inte/gmal specific updates and the bug is still present.

[Sos Oganessian (sos-u)]

Not that anyone seems to taking note of this bug, but for the sake of postarity, I done some digging and it seems to be related to the 3.5 kernel update. A simple revert to 3.2 kernel will solve the bug, if you are using 12.04 anyway.

[penalvch (penalvch)]

Sos Oganessian, 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

Please note, given that the information from the prior release is already available, doing this on a release prior to the development one would not be helpful.

If reproducible, could you also 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-rc7

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.

[Launchpad Janitor (janitor)]

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