compiz crashed with SIGSEGV in nux::ROProperty<std::string>::operator std::string()

[Andrew G]

7th October daily build Oneiric
Machine Lenovo Edge 11 Laptop
I do not know anything about the Compiz crash (machine stil working ok) - just saw a message asking me to file a bug report.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: libnux-1.0-0 1.14.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: fglrx wl
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
Date: Sun Oct 9 17:42:09 2011
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20111007.1)
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fccc5ea6ac0 <_ZNK3nux10ROPropertyISsEcvSsEv+16>: mov 0x8(%rcx),%rdx
 PC (0x7fccc5ea6ac0) ok
 source "0x8(%rcx)" (0x00000009) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nux
StacktraceTop:
 nux::ROProperty<std::string>::operator std::string() const () from /usr/lib/compiz/libunityshell.so
 unity::dash::ResultViewGrid::OnOnKeyNavFocusChange(nux::Area*) () from /usr/lib/compiz/libunityshell.so
 sigc::internal::signal_emit1<void, nux::Area*, sigc::nil>::emit(sigc::internal::signal_impl*, nux::Area* const&) () from /usr/lib/libnux-1.0.so.0
 nux::WindowCompositor::SetKeyFocusArea(nux::InputArea*) () from /usr/lib/libnux-1.0.so.0
 nux::WindowCompositor::MouseEventCycle(nux::Event&) () from /usr/lib/libnux-1.0.so.0
Title: compiz crashed with SIGSEGV in nux::ROProperty<std::string>::operator std::string()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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