ATI and Compiz max cpu usage when screen in standby mode bug

[George]

Does anybody else encounter the bug where if you use the drivers installed by Jockey and the screen goes into sleep (blacks out) that compiz then maxes one of the cores of the CPU?

I am running 12.04 on a Dell laptop with an ATI display. If I use the proprietary driver this happens as soon as the screen blacks out. This makes the laptop to become hot and noisy as well as the battery doesn't last.

The problem is that as soon as you move the mouse or press a key the screen comes on and then compiz usage returns to normal. The only way to verify this bug that I know of is to log in via ssh to the machine which screen has gone into standby mode and then run htop.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: xorg 1:7.6+12ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
NonfreeKernelModules: wl
.tmp.unity.support.test.0:

ApportVersion: 2.0.1-0ubuntu2
Architecture: amd64
CompizPlugins: [core,composite,opengl,decor,imgpng,regex,gnomecompat,vpswitch,animation,obs,unitymtgrabhandles,workarounds,mousepoll,compiztoolbox,place,move,wall,grid,resize,session,expo,snap,ezoom,fade,scale,unityshell]
CompositorRunning: compiz
Date: Thu Apr 12 21:29:13 2012
DistUpgraded: Fresh install
DistroCodename: precise
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 5.100.82.38+bdcom, 3.2.0-22-generic, x86_64: installed
 bcmwl, 5.100.82.38+bdcom, 3.2.0-23-generic, x86_64: installed
 vboxhost, 4.1.12, 3.2.0-22-generic, x86_64: installed
 vboxhost, 4.1.12, 3.2.0-23-generic, x86_64: installed
ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu
GraphicsCard:
 Advanced Micro Devices [AMD] nee ATI Manhattan [Mobility Radeon HD 5400 Series] [1002:68e0] (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:0413]
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120405)
MachineType: Dell Inc. Studio 1558
ProcEnviron:
 LANGUAGE=en_ZA:en
 PATH=(custom, no user)
 LANG=en_ZA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic root=UUID=df1d4d1b-c042-4fce-ba1c-d3c114e271d8 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/12/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 0874P6
dmi.board.vendor: Dell Inc.
dmi.board.version: A11
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A11
dmi.modalias: dmi:bvnDellInc.:bvrA11:bd10/12/2010:svnDellInc.:pnStudio1558:pvrA11:rvnDellInc.:rn0874P6:rvrA11:cvnDellInc.:ct8:cvrA11:
dmi.product.name: Studio 1558
dmi.product.version: A11
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.7.4-0ubuntu3
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.32-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2

[Filipe Manco (fmanco)]

This bug also affects me. I think this is a duplicate of Bug #969860.

[Launchpad Janitor (janitor)]

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

[George (george-labuschagne-gmail)]

Would I be able to pay a compiz dev to fix this bug? And if so ho much?

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 969860, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.