compiz crashed with SIGSEGV in sigc::internal::signal_emit0<void, sigc::nil>::emit()

[Dean Homer]

compiz crashed while switching to the already running program System Monitor.

Ubuntu release is Ubuntu Natty (development branch), Release: 11.04
Package that crashed compiz:
  Installed: 1:0.9.4git20110322-0ubuntu5
  Candidate: 1:0.9.4git20110322-0ubuntu5
  Version table:
 *** 1:0.9.4git20110322-0ubuntu5 0
        500 http://ca.archive.ubuntu.com/ubuntu/ natty/main i386 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: libnux-0.9-0 0.9.36-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-generic i686
Architecture: i386
CrashCounter: 1
Date: Sun Mar 27 08:22:09 2011
ExecutablePath: /usr/bin/compiz
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=en_CA:en
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x9ca3e40 <_ZN4sigc8internal12signal_emit0IvNS_3nilEE4emitEPNS0_11signal_implE+144>: mov 0x8(%esi),%eax
 PC (0x09ca3e40) ok
 source "0x8(%esi)" (0x00000808) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nux
StacktraceTop:
 sigc::internal::signal_emit0<void, sigc::nil>::emit(sigc::internal::signal_impl*) () from /usr/lib/compiz/libunityshell.so
 Launcher::EventLogic() () from /usr/lib/compiz/libunityshell.so
 Launcher::DrawContent(nux::GraphicsEngine&, bool) () from /usr/lib/compiz/libunityshell.so
 nux::View::ProcessDraw(nux::GraphicsEngine&, bool) () from /usr/lib/libnux-0.9.so.0
 nux::Layout::ProcessDraw(nux::GraphicsEngine&, bool) () from /usr/lib/libnux-0.9.so.0
Title: compiz crashed with SIGSEGV in sigc::internal::signal_emit0<void, sigc::nil>::emit()
UpgradeStatus: Upgraded to natty on 2011-03-22 (4 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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