compiz crashed with SIGSEGV in TfpTexture::bindTexImage()

[Kevin Carlson]

Ubuntu 12.10 Beta 64-bit, with Unity Desktop

This happened on a machine with Intel HD Graphics 3000, using nomodeset. The system would hang for a bit after closing an application (e.g. display settings or system monitor). I switched to a virtual terminal and back to Unity, and the screen was mostly black with some bits of the desktop visible. Moving the mouse would show the part of the desktop where the mouse was. Eventually, the system was able to recover, after closing Compiz.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: unity 6.4.0-0ubuntu6
ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3
Uname: Linux 3.5.0-14-generic x86_64
ApportVersion: 2.5.1-0ubuntu7
Architecture: amd64
Date: Sun Sep 16 16:58:09 2012
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
ProcCmdline: compiz
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f0221d7a696: movdqu -0x10(%rsi),%xmm0
 PC (0x7f0221d7a696) ok
 source "-0x10(%rsi)" (0x1fe7bc60) not located in a known VMA region (needed readable region)!
 destination "%xmm0" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
 ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
 TfpTexture::bindTexImage(unsigned long const&) () from /usr/lib/compiz/libopengl.so
 TfpTexture::enable(GLTexture::Filter) () from /usr/lib/compiz/libopengl.so
Title: compiz crashed with SIGSEGV in TfpTexture::bindTexImage()
UpgradeStatus: Upgraded to quantal on 2012-09-16 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare 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 #1051072, 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.