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

[Tony Mugan]

Binary package hint: unity

When trying to switch on Wobbly Windows in CompizConfig Settings Manager, I got this crash.

Wobbly Windows does appear to have worked though and there are no other issues obvious to me so maybe it restarted successfully?

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: unity 3.6.8-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.38-7.38-generic 2.6.38
Uname: Linux 2.6.38-7-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Sat Mar 26 07:51:37 2011
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110319)
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f9cdfeec2f6 <_ZNK4sigc11signal_base4implEv+22>: mov 0x8(%rdi),%rbx
 PC (0x7f9cdfeec2f6) ok
 source "0x8(%rdi)" (0x000000e8) not located in a known VMA region (needed readable region)!
 destination "%rbx" 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: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Tony Mugan (tmugan)]

This was with Natty Alpha with all latest updates to 20110326

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