Compiz crashed on me in the middle of my oneiric→natty upgrade. I fired up a shell and tried to re-start compiz in debug mode, using a command from my history. It crashed again, and I gave up and fired up metacity just so that I could move windows around and ensure that the update-manager was still running.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: libnux-2.0-0 2.2.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-14.23-generic 3.2.3
Uname: Linux 3.2.0-14-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Mon Feb 6 09:27:46 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/compiz
ProcCmdline: compiz
ProcEnviron:
PATH=(custom, user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f62bbbec1e7 <_ZNK3nux12NTextureData10GetSurfaceEi+7>: mov (%rax,%rsi,8),%rax
PC (0x7f62bbbec1e7) ok
source "(%rax,%rsi,8)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nux
StacktraceTop:
nux::NTextureData::GetSurface(int) const () from /usr/lib/libnux-image-2.0.so.0
nux::CreateTexture2DFromPixbuf(_GdkPixbuf*, bool) () from /usr/lib/libnux-graphics-2.0.so.0
WindowButton::WindowButton(unity::panel::WindowButtonType) () from /usr/lib/compiz/libunityshell.so
unity::WindowButtons::WindowButtons() () from /usr/lib/compiz/libunityshell.so
unity::PanelMenuView::PanelMenuView(int) () from /usr/lib/compiz/libunityshell.so
Title: compiz crashed with SIGSEGV in nux::NTextureData::GetSurface()
UpgradeStatus: Upgraded to precise on 2012-02-06 (0 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare staff
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 #921130, 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.