compiz crashed with SIGSEGV in nux::Property<int>::operator=()

[jhfhlkjlj]

I had removed my secondary monitor from the configuration, noticed that my wacom tablet (which was set to sync to only the primary monitor) was still 'synced': The whole tablet spanned only half of the monitor remaining. When I turned off the sync-to-monitor option, it croaked.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity 5.6.0-0ubuntu3
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Wed Mar 14 02:10:14 2012
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120216)
ProcCmdline: compiz
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fbece19d23d <_ZN3nux8PropertyIiEaSERKi+45>: mov 0x8(%rdi),%rax
 PC (0x7fbece19d23d) ok
 source "0x8(%rdi)" (0x4040d45681ecd4b1) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 nux::Property<int>::operator=(int const&) () from /usr/lib/compiz/libunityshell.so
 unity::ui::Decaymulator::OnDecayTimeout(void*) () from /usr/lib/compiz/libunityshell.so
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: compiz crashed with SIGSEGV in nux::Property<int>::operator=()
UpgradeStatus: Upgraded to precise on 2012-03-14 (0 days ago)
UserGroups: adm cdrom dip 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 #937560, 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.