compiz crashed with SIGSEGV in nux::BaseWindow::IsModal()

[Barry Fishman]

I was right clicking on the left side of the screen toolbar when the application (vlc) had frozen. I've just started using
Natty and am still trying to figure out how to do things.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: libnux-0.9-0 0.9.38-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-generic x86_64
Architecture: amd64
Date: Sat Apr 2 17:57:19 2011
ExecutablePath: /usr/bin/compiz
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=en_US:en
 LC_COLLATE=C
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fe93204b950 <_ZNK3nux10BaseWindow7IsModalEv>: movzbl 0x44a(%rdi),%eax
 PC (0x7fe93204b950) ok
 source "0x44a(%rdi)" (0x0000044a) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nux
StacktraceTop:
 nux::BaseWindow::IsModal() const () from /usr/lib/libnux-0.9.so.0
 nux::WindowCompositor::RenderTopViews(bool, std::list<nux::ObjectWeakPtr<nux::BaseWindow>, std::allocator<nux::ObjectWeakPtr<nux::BaseWindow> > >&, bool, bool) () from /usr/lib/libnux-0.9.so.0
 nux::WindowCompositor::Draw(bool, bool) () from /usr/lib/libnux-0.9.so.0
 nux::WindowThread::RenderInterfaceFromForeignCmd(nux::Rect*) () from /usr/lib/libnux-0.9.so.0
 UnityScreen::paintDisplay(CompRegion const&) () from /usr/lib/compiz/libunityshell.so
Title: compiz crashed with SIGSEGV in nux::BaseWindow::IsModal()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare staff util

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