Quantal in Vbox
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 x86_64
ApportVersion: 2.4-0ubuntu8
Architecture: amd64
CrashCounter: 1
Date: Fri Aug 17 15:35:42 2012
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120627)
ProcCmdline: compiz
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f7d2de1efb7: movaps %xmm1,-0x10(%rdi)
PC (0x7f7d2de1efb7) ok
source "%xmm1" ok
destination "-0x10(%rdi)" (0x10a179d10) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: compiz
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::enable(GLTexture::Filter) () from /usr/lib/compiz/libopengl.so
GLWindow::glDrawTexture(GLTexture*, GLFragment::Attrib&, unsigned int) () from /usr/lib/compiz/libopengl.so
Title: compiz crashed with SIGSEGV in TfpTexture::enable()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
XsessionErrors:
gnome-session[1651]: WARNING: Application 'compiz.desktop' killed by signal 11
gnome-session[1651]: WARNING: App 'compiz.desktop' respawning too quickly
gnome-session[1651]: CRITICAL: We failed, but the fail whale is dead. Sorry....
gnome-session[1651]: WARNING: Application 'compiz.desktop' killed by signal 11
gnome-session[1651]: WARNING: App 'compiz.desktop' respawning too quickly
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 #1019834, 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.