compiz crashed with SIGSEGV in __strstr_ia32()

[Blair Chasteen]

this is bug report is a repeat of my last one but with fully downloaded symbol library

other bug https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1037501

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: compiz-core 1:0.9.8+bzr3249-0ubuntu4
ProcVersionSignature: Ubuntu 3.5.0-10.10-generic 3.5.1
Uname: Linux 3.5.0-10-generic i686
NonfreeKernelModules: fglrx
ApportVersion: 2.4-0ubuntu8
Architecture: i386
CheckboxSubmission: a8e76548fbc60a2f5426ec4a1cb70fc9
CheckboxSystem: c541d13ea4f205f2fd751f76ed21105b
CrashCounter: 1
Date: Thu Aug 16 06:26:24 2012
ExecutablePath: /usr/bin/compiz
ExecutableTimestamp: 1345046380
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
ProcCmdline: Compiz
ProcCwd: /home/darkrain
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb741f946 <__strstr_ia32+22>: movzbl 0x0(%ebp),%eax
 PC (0xb741f946) ok
 source "0x0(%ebp)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
 __strstr_ia32 (haystack_start=0x0, needle_start=0xb60e732f "GLX_SGIX_fbconfig") at ../string/strstr.c:63
 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
Title: compiz crashed with SIGSEGV in __strstr_ia32()
UpgradeStatus: Upgraded to quantal on 2012-08-16 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev root sambashare vboxusers

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