compiz crashed with SIGSEGV in glXGetConfig()

[Rehan Khamaruddin]

Does this on login. Every time. Happened after I installed cairo-dock but I am not in the cairo-dock session. Nor had I started cairo-dock. Reboot did not fix the problem.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: compiz-core 1:0.9.7.6-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.0.1-0ubuntu4
Architecture: amd64
CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CompositorRunning: compiz
CurrentDmesg:
 [ 423.288444] show_signal_msg: 54 callbacks suppressed
 [ 423.288448] compiz[2299]: segfault at 8 ip 00007f7a5020620c sp 00007fff91887270 error 4 in libGL.so.1.2[7f7a501e6000+5d000]
 [ 423.295464] cairo-dock[2563]: segfault at 8 ip 00007f1a4c53d20c sp 00007fff5c78f3d0 error 4 in libGL.so.1.2[7f1a4c51d000+5d000]
Date: Tue Apr 17 21:32:05 2012
DistUpgraded: Fresh install
DistroCodename: precise
DistroVariant: ubuntu
ExecutablePath: /usr/bin/compiz
GraphicsCard:
 Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Elitegroup Computer Systems Device [1019:2639]
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
MachineType: ECS G31T-M
ProcCmdline: Compiz
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic root=UUID=a79e6b57-c2db-4617-9cdd-8911c65be0e7 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7f7a5020620c: cmpl $0x1,0x8(%rax)
 PC (0x7f7a5020620c) ok
 source "$0x1" ok
 destination "0x8(%rax)" (0x00000008) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1
 ?? () from /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1
 glXGetConfig () from /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1
 GLScreen::GLScreen(CompScreen*) () from /usr/lib/compiz/libopengl.so
 PluginClassHandler<GLScreen, CompScreen, 4>::get(CompScreen*) () from /usr/lib/compiz/libopengl.so
Title: compiz crashed with SIGSEGV in glXGetConfig()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 01/07/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080014
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: G31T-M
dmi.board.vendor: ECS
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: ECS
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080014:bd01/07/2009:svnECS:pnG31T-M:pvr1.0:rvnECS:rnG31T-M:rvr1.0:cvnECS:ct3:cvr1.0:
dmi.product.name: G31T-M
dmi.product.version: 1.0
dmi.sys.vendor: ECS
version.compiz: compiz 1:0.9.7.6-0ubuntu1
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

[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 #931939, 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.