compiz crashed with SIGSEGV in GLScreen::GLScreen()

[Neal Cloud]

desktop crashed on closing firefox,

1. closed firefox once desktop blinked out and came back.
2. closed firefox again desktop blinked out and came back but no unity and compiz...

having trubble geting unity working without reinstall...

hope this helps.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: compiz-core 1:0.9.8.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-14.17-generic 3.5.3
Uname: Linux 3.5.0-14-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.5.1-0ubuntu7
Architecture: amd64
Date: Fri Sep 14 16:57:38 2012
DistUpgraded: Fresh install
DistroCodename: quantal
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 5.100.82.112+bdcom, 3.5.0-14-generic, x86_64: installed
 nvidia-current-updates, 304.43, 3.5.0-14-generic, x86_64: installed
ExecutablePath: /usr/bin/compiz
GraphicsCard:
 Advanced Micro Devices [AMD] nee ATI Cape Verde [Radeon HD 7700 Series] [1002:683d] (prog-if 00 [VGA controller])
   Subsystem: PC Partner Limited Device [174b:e214]
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120913.3)
MachineType: System manufacturer System Product Name
ProcCmdline: Compiz
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-14-generic root=UUID=5b109bb3-015b-4ba6-96f7-29cb00612630 ro quiet splash
SegvAnalysis:
 Segfault happened at: 0x7f37068cb458: movzbl (%rdi),%eax
 PC (0x7f37068cb458) ok
 source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 GLScreen::GLScreen(CompScreen*) () from /usr/lib/compiz/libopengl.so
 PluginClassHandler<GLScreen, CompScreen, 5>::get(CompScreen*) () from /usr/lib/compiz/libopengl.so
 CompPlugin::VTableForScreenAndWindow<GLScreen, GLWindow>::initScreen(CompScreen*) () from /usr/lib/compiz/libopengl.so
 CompManager::initPlugin(CompPlugin*) () from /usr/lib/libcompiz_core.so.ABI-20120603
Title: compiz crashed with SIGSEGV in GLScreen::GLScreen()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 08/01/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1504
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8Z77-V DELUXE
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1504:bd08/01/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.8.0-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.39-0ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.0~git20120903.e1673d20.is.git20120821.c1114c61-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.0~git20120903.e1673d20.is.git20120821.c1114c61-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120713.6ef1ad6a-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.7-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu1

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