compiz crashed with SIGSEGV in nux::GpuDevice::GetGpuInfo()

[MarkJBobak]

Binary package hint: compiz

I had enabled Desktop Cube, which in turn disabled Desktop Wall. I then clicked Desktop Wall, thinking it would disable Desktop Cube, and compiz appeared to crash. My windows all lost decorations/borders, and things stopped responding.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: libnux-0.9-0 0.9.44-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-8.42~ppa2-lowlatency 2.6.38.2
Uname: Linux 2.6.38-8-lowlatency x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
CrashCounter: 1
Date: Fri Apr 15 16:55:25 2011
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110330)
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f83df9e4050 <_ZN3nux9GpuDevice10GetGpuInfoEv>: mov 0xc0(%rdi),%rax
 PC (0x7f83df9e4050) ok
 source "0xc0(%rdi)" (0x000000c0) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nux
StacktraceTop:
 nux::GpuDevice::GetGpuInfo() () from /usr/lib/libnux-graphics-0.9.so.0
 nux::GpuDevice::CreateSystemCapableTexture() () from /usr/lib/libnux-graphics-0.9.so.0
 PanelMenuView::Refresh() () from /usr/lib/compiz/libunityshell.so
 PanelMenuView::OnActiveWindowChanged(_BamfView*, _BamfView*) () from /usr/lib/compiz/libunityshell.so
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: compiz crashed with SIGSEGV in nux::GpuDevice::GetGpuInfo()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout disk lpadmin plugdev sambashare vboxusers

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #761368, 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.