compiz crashed with SIGSEGV in compiz::opengl::bindTexImageGLX()

[Jerome Rasky]

Problem reported by apport

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: unity 7.1.0+13.10.20130903.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
Uname: Linux 3.11.0-4-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.12.1-0ubuntu3
Architecture: amd64
Date: Fri Sep 6 22:52:58 2013
ExecutablePath: /usr/bin/compiz
ExecutableTimestamp: 1377717749
InstallationDate: Installed on 2013-09-07 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130906)
MarkForUpload: True
ProcCmdline: compiz
ProcCwd: /home/jerome
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f08c6132ef0 <__memmove_ssse3_back+80>: movdqu (%rsi),%xmm0
 PC (0x7f08c6132ef0) ok
 source "(%rsi)" (0xffffffff8f1ba938) not located in a known VMA region (needed readable region)!
 destination "%xmm0" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
 ?? ()
 compiz::opengl::bindTexImageGLX(ServerGrabInterface*, unsigned long, unsigned long, boost::function<bool (unsigned long)> const&, boost::function<void (unsigned long)> const&, boost::function<void ()> const&, compiz::opengl::_PixmapSource) () from /usr/lib/compiz/libopengl.so
Title: compiz crashed with SIGSEGV in compiz::opengl::bindTexImageGLX()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: sudo

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