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

[dondad]

After restart for latest update

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: libnux-0.9-0 0.9.44-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
CheckboxSubmission: 511f3e35fc4b9d67e199e5e74c6e25dc
CheckboxSystem: 2a6f54df59af338184485e85cbcf0d32
CrashCounter: 1
Date: Sat Apr 16 09:26:17 2011
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta i386 (20100901.1)
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_CA.UTF-8
 LC_MESSAGES=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x1315cb7 <_ZN3nux9GpuDevice10GetGpuInfoEv+7>: mov 0x70(%eax),%eax
 PC (0x01315cb7) ok
 source "0x70(%eax)" (0x00000070) not located in a known VMA region (needed readable region)!
 destination "%eax" 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
 ?? () from /usr/lib/compiz/libunityshell.so
Title: compiz crashed with SIGSEGV in nux::GpuDevice::GetGpuInfo()
UpgradeStatus: Upgraded to natty on 2011-04-01 (15 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors: (nautilus:1464): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed

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