compiz crashed with SIGSEGV in CompositeScreen::compositingActive()

[IKT]

crashed when trying to play around with cairo dock

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: compiz-core 1:0.9.7.0~bzr2995-0ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,resize,imgpng,mousepoll,snap,move,grid,regex,vpswitch,gnomecompat,place,session,wall,animation,workarounds,expo,fade,ezoom,scale,unityshell,dbus]
CompositorRunning: compiz
Date: Sun Feb 19 22:34:00 2012
DistUpgraded: Fresh install
DistroCodename: precise
DistroVariant: ubuntu
DuplicateOf: https://bugs.launchpad.net/bugs/901211
ExecutablePath: /usr/bin/compiz
GraphicsCard:
 Advanced Micro Devices [AMD] nee ATI Wrestler [Radeon HD 6310] [1002:9802] (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:3387]
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120201.1)
MachineType: Hewlett-Packard HP Pavilion dm1 Notebook PC
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-17-generic root=UUID=d22c2bb8-efe4-4317-b9c1-bf0e94b7da2b ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7ff726f60a20 <_ZN15CompositeScreen17compositingActiveEv>: mov 0x60(%rdi),%rax
 PC (0x7ff726f60a20) ok
 source "0x60(%rdi)" (0x00000060) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
 CompositeScreen::compositingActive() () from /usr/lib/compiz/libcomposite.so
 PrivateCompositeWindow::PrivateCompositeWindow(CompWindow*, CompositeWindow*) () from /usr/lib/compiz/libcomposite.so
 CompositeWindow::CompositeWindow(CompWindow*) () from /usr/lib/compiz/libcomposite.so
 PluginClassHandler<CompositeWindow, CompWindow, 4>::get(CompWindow*) () from /usr/lib/compiz/libopengl.so
 PrivateGLWindow::PrivateGLWindow(CompWindow*, GLWindow*) () from /usr/lib/compiz/libopengl.so
Title: compiz crashed with SIGSEGV in CompositeScreen::compositingActive()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 08/04/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.01
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 3387
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 36.0A
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.01:bd08/04/2011:svnHewlett-Packard:pnHPPaviliondm1NotebookPC:pvr0697100000204600000320100:rvnHewlett-Packard:rn3387:rvr36.0A:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion dm1 Notebook PC
dmi.product.version: 0697100000204600000320100
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.7.0~bzr2995-0ubuntu4
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.30-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 8.0~rc2-0ubuntu5
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 8.0~rc2-0ubuntu5
version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.99.901+git20120126-0ubuntu2
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

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #833729, so 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. Please continue to report any other bugs you may find.