compiz crashed with SIGSEGV in GLScreen::GLScreen()

[dekki]

After an update to 12.10 beta
Crash occurs during login, file manager crashes as well.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: compiz-core 1:0.9.8.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3
Uname: Linux 3.5.0-14-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.5.1-0ubuntu7
Architecture: amd64
Date: Sun Sep 16 19:25:59 2012
DistUpgraded: 2012-09-16 19:24:58,001 DEBUG enabling apt cron job
DistroCodename: quantal
DistroVariant: ubuntu
DkmsStatus:
 fglrx-updates, 8.960, 3.2.0-30-generic, x86_64: installed
 fglrx-updates, 8.960, 3.5.0-14-generic, x86_64: installed
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/compiz
GraphicsCard:
 Advanced Micro Devices [AMD] nee ATI Device [1002:68c9] (prog-if 00 [VGA controller])
   Subsystem: Advanced Micro Devices [AMD] nee ATI Device [1002:210a]
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
JockeyStatus:
 kmod:fglrx - Video driver for the AMD graphics accelerators (Proprietary, Disabled, Not in use)
 kmod:fglrx_updates - ATI Fire GL (Proprietary, Enabled, Not in use)
MachineType: FUJITSU CELSIUS W410
ProcCmdline: Compiz
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.5.0-14-generic root=UUID=f1c4d4ce-ee53-4a2b-83f9-19a0de17dc74 ro rootflags=subvol=@ quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7f9bd2f28458: movzbl (%rdi),%eax
 PC (0x7f9bd2f28458) 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-16 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 07/29/2011
dmi.bios.vendor: FUJITSU // American Megatrends Inc.
dmi.bios.version: V4.6.4.0 R1.14.0 for D3062-A1x
dmi.board.name: D3062-A1
dmi.board.vendor: FUJITSU
dmi.board.version: S26361-D3062-A1
dmi.chassis.type: 6
dmi.chassis.vendor: FUJITSU
dmi.chassis.version: C$W400
dmi.modalias: dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV4.6.4.0R1.14.0forD3062-A1x:bd07/29/2011:svnFUJITSU:pnCELSIUSW410:pvr:rvnFUJITSU:rnD3062-A1:rvrS26361-D3062-A1:cvnFUJITSU:ct6:cvrC$W400:
dmi.product.name: CELSIUS W410
dmi.sys.vendor: FUJITSU
version.compiz: compiz 1:0.9.8.0-0ubuntu1
version.fglrx-installer: fglrx-installer N/A
version.ia32-libs: ia32-libs 20090808ubuntu36
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.