compiz crashed with SIGSEGV in sigc::signal_base::impl()

[Fabien Tassin]

Binary package hint: compiz

crashed just when i disabled the Grid plugin in the ccsm "window management" section.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: compiz-core 1:0.9.4-0ubuntu4
ProcVersionSignature: Ubuntu 2.6.38-6.34-generic 2.6.38-rc7
Uname: Linux 2.6.38-6-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Tue Mar 15 01:29:14 2011
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100331)
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/usr/bin/tcsh
SegvAnalysis:
 Segfault happened at: 0xd36e3d <_ZNK4sigc11signal_base4implEv+29>: mov 0x4(%edi),%esi
 PC (0x00d36e3d) ok
 source "0x4(%edi)" (0x0000007c) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
 sigc::signal_base::impl() const () from /usr/lib/libsigc-2.0.so.0
 sigc::signal_base::connect(sigc::slot_base const&) () from /usr/lib/libsigc-2.0.so.0
 connect (this=0x88036b8, screen=0x86ca4b8) at /usr/include/sigc++-2.0/sigc++/signal.h:2659
 UnityScreen::UnityScreen (this=0x88036b8, screen=0x86ca4b8) at /build/buildd/unity-3.6.4/src/unityshell.cpp:753
 VTableForScreenAndWindow<UnityScreen, UnityWindow>::initScreen (this=0x8713ae8, s=0x86ca4b8) at /usr/include/compiz/core/plugin.h:238
Title: compiz crashed with SIGSEGV in sigc::signal_base::impl()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare wireshark

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