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

[[e-mail]]

was launching photoshop through wine

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: libnux-0.9-0 0.9.36-0ubuntu1 [modified: usr/lib/libnux-0.9.so.0.932.4 usr/lib/libnux-core-0.9.so.0.932.4 usr/lib/libnux-graphics-0.9.so.0.932.4 usr/lib/libnux-image-0.9.so.0.932.4]
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic-pae 2.6.38
Uname: Linux 2.6.38-7-generic-pae i686
Architecture: i386
CrashCounter: 1
Date: Wed Mar 30 23:17:26 2011
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb5735e40 <_ZN4sigc8internal12signal_emit0IvNS_3nilEE4emitEPNS0_11signal_implE+144>: mov 0x8(%esi),%eax
 PC (0xb5735e40) ok
 source "0x8(%esi)" (0x00000008) 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-29 (1 days ago)
UserGroups: adm admin audio cdrom dialout floppy fuse lpadmin netdev plugdev sambashare tape vboxusers video

[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.