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

[Ryota Ozaki]

Binary package hint: compiz-core

It happens when I turn Window Management/Grid on/off through compiz-decorator. It's reproducible.

I'm not sure that the bug is same as https://bugs.launchpad.net/ubuntu/+source/unity/+bug/742326 and https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/750008 .

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: unity 3.8.2-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: Tue Apr 5 12:49:54 2011
ExecutablePath: /usr/bin/compiz
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=ja_JP:en_US:en
 PATH=(custom, user)
 LANG=ja_JP.UTF-8
 SHELL=/usr/bin/zsh
SegvAnalysis:
 Segfault happened at: 0x4a2e3d <_ZNK4sigc11signal_base4implEv+29>: mov 0x4(%edi),%esi
 PC (0x004a2e3d) 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: unity
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
 UnityScreen::UnityScreen(CompScreen*) () from /usr/lib/compiz/libunityshell.so
 CompPlugin::VTableForScreenAndWindow<UnityScreen, UnityWindow>::initScreen(CompScreen*) () from /usr/lib/compiz/libunityshell.so
 CompManager::initPlugin(CompPlugin*) ()
Title: compiz crashed with SIGSEGV in sigc::signal_base::impl()
UpgradeStatus: Upgraded to natty on 2011-04-01 (3 days ago)
UserGroups: adm admin audio cdrom dialout dip floppy libvirtd lpadmin netdev plugdev powerdev scanner video

[Andrew Constantine (andrewmc)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 744198, so it 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. Feel free to continue to report any other bugs you may find.