compiz crashed with SIGSEGV in CompAction::initiate()

[dc]

Compiz crashed after adjusting settings in CCSM.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: unity 6.12.0daily13.03.29.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4
Uname: Linux 3.8.0-15-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
Date: Sat Mar 30 09:48:37 2013
ExecutablePath: /usr/bin/compiz
InstallationDate: Installed on 2012-04-27 (337 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120423)
MarkForUpload: True
ProcCmdline: compiz
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fda2380323d <_ZN10CompAction8initiateEv+13>: mov 0x8(%rdi),%rdx
 PC (0x7fda2380323d) ok
 source "0x8(%rdi)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 CompAction::initiate() () from /usr/lib/libcompiz_core.so.ABI-20130125
 unity::MultiActionList::Initiate(std::string const&, std::vector<CompOption, std::allocator<CompOption> > const&, int) const () from /usr/lib/compiz/libunityshell.so
 unity::MultiActionList::InitiateAll(std::vector<CompOption, std::allocator<CompOption> > const&, int) const () from /usr/lib/compiz/libunityshell.so
 unity::PluginAdapter::InitiateExpo() () from /usr/lib/compiz/libunityshell.so
 unity::launcher::LauncherIcon::Activate(unity::launcher::ActionArg) () from /usr/lib/compiz/libunityshell.so
Title: compiz crashed with SIGSEGV in CompAction::initiate()
UpgradeStatus: Upgraded to raring on 2013-03-29 (1 days ago)
UserGroups: adm cdrom debian-tor dip libvirtd lpadmin plugdev sambashare sudo

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