compiz crashed with SIGSEGV in nux::WindowThread::QueueObjectLayout()

[Sergey "Shnatsel" Davidoff]

I got this crash after enabling "resize info" plugin in CCSM. The plugin seems to work fine though.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: libnux-2.0-0 2.4.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
ApportVersion: 1.94.1-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Fri Mar 9 01:18:03 2012
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120303)
ProcCmdline: compiz
ProcEnviron:
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f2cbc6c2788 <_ZN3nux12WindowThread17QueueObjectLayoutEPNS_4AreaE+40>: cmp %rbx,0x10(%rax)
 PC (0x7f2cbc6c2788) ok
 source "%rbx" ok
 destination "0x10(%rax)" (0x642f5f6576697274) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: nux
StacktraceTop:
 nux::WindowThread::QueueObjectLayout(nux::Area*) () from /usr/lib/libnux-2.0.so.0
 unity::PanelIndicatorsView::OnEntryRefreshed(unity::PanelIndicatorEntryView*) () from /usr/lib/compiz/libunityshell.so
 unity::PanelIndicatorEntryView::Refresh() () from /usr/lib/compiz/libunityshell.so
 unity::indicator::Entry::setLabel(std::string const&, bool, bool) () from /usr/lib/libunity-core-5.0.so.5
 ?? () from /usr/lib/libunity-core-5.0.so.5
Title: compiz crashed with SIGSEGV in nux::WindowThread::QueueObjectLayout()
UpgradeStatus: No upgrade log present (probably fresh install)
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 #930832, 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.