compiz crashed on enabling the opacity, brightness and saturation plugin with SIGSEGV in unity::glib::Source::IsRunning()

[Mike]

Hello,

Just enabled the opacity, brightness and saturation plugin in CCSM and got the crash.

Ubuntu 15.04, all updates, xorg from edgers though.

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: unity 7.3.1+15.04.20150227-0ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
Uname: Linux 3.19.0-9-generic x86_64
ApportVersion: 2.16.2-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Mar 14 23:47:29 2015
ExecutablePath: /usr/bin/compiz
InstallationDate: Installed on 2013-10-10 (520 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
ProcCmdline: compiz
SegvAnalysis:
 Segfault happened at: 0x7f5516e403d3 <_ZNK5unity4glib6Source9IsRunningEv+3>: mov 0x18(%rdi),%rdi
 PC (0x7f5516e403d3) ok
 source "0x18(%rdi)" (0x00000038) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 unity::glib::Source::IsRunning() const () from /usr/lib/libunity-core-6.0.so.9
 unity::XdndStartStopNotifierImp::DndTimeoutSetup() () from /usr/lib/compiz/libunityshell.so
 sigc::internal::signal_emit1<void, unsigned long, sigc::nil>::emit(sigc::internal::signal_impl*, unsigned long const&) () from /usr/lib/compiz/libunityshell.so
 unity::PluginAdapter::Notify(CompWindow*, CompWindowNotify) () from /usr/lib/compiz/libunityshell.so
 unity::UnityWindow::windowNotify(CompWindowNotify) () from /usr/lib/compiz/libunityshell.so
Title: compiz crashed with SIGSEGV in unity::glib::Source::IsRunning()
UpgradeStatus: Upgraded to vivid on 2015-03-01 (13 days ago)
UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo wireshark

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1425085, 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.