compiz crashed with SIGSEGV in GLScreen::GLScreen()

[Jaromir Obr]

I logged in upon upgrade from 12.04 -> 12.10

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: compiz-core 1:0.9.8.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
Uname: Linux 3.5.0-13-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.5.1-0ubuntu7
Architecture: amd64
Date: Sat Sep 8 00:15:46 2012
DistUpgraded: 2012-09-08 00:13:12,806 DEBUG enabling apt cron job
DistroCodename: quantal
DistroVariant: ubuntu
DkmsStatus:
 fglrx, 8.960, 3.2.0-30-generic, x86_64: installed
 fglrx, 8.960, 3.5.0-13-generic, x86_64: installed
 virtualbox, 4.1.18, 3.2.0-30-generic, x86_64: installed
 virtualbox, 4.1.18, 3.5.0-13-generic, x86_64: installed
ExecutablePath: /usr/bin/compiz
GraphicsCard:
 Advanced Micro Devices [AMD] nee ATI RV620 [Mobility Radeon HD 3400 Series] [1002:95c4] (prog-if 00 [VGA controller])
   Subsystem: Toshiba America Info Systems Device [1179:ff62]
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64+mac (20111011)
JockeyStatus:
 kmod:fglrx - ATI Fire GL (Proprietary, Enabled, In use)
 kmod:fglrx_updates - Video driver for the AMD graphics accelerators (Proprietary, Disabled, Not in use)
MachineType: TOSHIBA Satellite A300D
ProcCmdline: Compiz
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-13-generic root=/dev/mapper/Data-Root ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7f93b754b9c4: movzbl (%rdi),%eax
 PC (0x7f93b754b9c4) 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: Upgraded to quantal on 2012-09-07 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers wireshark
dmi.bios.date: 09/01/2009
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 2.10
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: AMD
dmi.chassis.version: None
dmi.modalias: dmi:bvnInsydeCorp.:bvr2.10:bd09/01/2009:svnTOSHIBA:pnSatelliteA300D:pvrPSAHCE-00F00JCZ:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnAMD:ct10:cvrNone:
dmi.product.name: Satellite A300D
dmi.product.version: PSAHCE-00F00JCZ
dmi.sys.vendor: TOSHIBA
version.compiz: compiz 1:0.9.8.0-0ubuntu1
version.fglrx-installer: fglrx-installer N/A
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 N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.6-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.1-4~ubuntu1

[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.