compiz crashed with SIGSEGV in GLScreen::GLScreen()

[Angel Guzman Maeso]

Fully update with quantal alpha 3. While I am working the desktop crash and apport catch this error.

After, doing a unity --reset I cannot start again unity (same error), so I only can do a "metacity --replace".

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: compiz-core 1:0.9.8+bzr3249-0ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-1.1-generic 3.5.0-rc3
Uname: Linux 3.5.0-1-generic i686
ApportVersion: 2.4-0ubuntu6
Architecture: i386
CrashCounter: 1
Date: Mon Aug 6 19:05:51 2012
ExecutablePath: /usr/bin/compiz
InstallationMedia:

ProcCmdline: Compiz --replace
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb74942f5 <__strstr_sse42+37>: movzbl (%eax),%edx
 PC (0xb74942f5) ok
 source "(%eax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
 GLScreen::GLScreen(CompScreen*) () from /usr/lib/compiz/libopengl.so
 PluginClassHandler<GLScreen, CompScreen, 4>::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-20120526
 CompPlugin::push(CompPlugin*) () from /usr/lib/libcompiz_core.so.ABI-20120526
Title: compiz crashed with SIGSEGV in GLScreen::GLScreen()
UpgradeStatus: Upgraded to quantal on 2012-06-05 (62 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare tape vboxusers video

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