compiz crashed with SIGSEGV in nux::Area::FindKeyFocusArea()

[vnieto]

When i use ctrl+alt+ -> on unity with cube desktop

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: libnux-1.0-0 1.8.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-11.17-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.22.1-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Tue Sep 13 20:09:34 2011
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
ProcCmdline: compiz
SegvAnalysis:
 Segfault happened at: 0x7fbe0f02f298 <_ZN3nux4Area16FindKeyFocusAreaEjmm+24>: mov 0x128(%rax),%rax
 PC (0x7fbe0f02f298) ok
 source "0x128(%rax)" (0x00000129) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nux
StacktraceTop:
 nux::Area::FindKeyFocusArea(unsigned int, unsigned long, unsigned long) () from /usr/lib/libnux-1.0.so.0
 nux::WindowCompositor::FindKeyFocusArea(nux::NuxEventType, unsigned int, unsigned int, nux::InputArea**, nux::BaseWindow**) () from /usr/lib/libnux-1.0.so.0
 nux::WindowCompositor::KeyboardEventCycle(nux::Event&) () from /usr/lib/libnux-1.0.so.0
 nux::WindowCompositor::ProcessEvent(nux::Event&) () from /usr/lib/libnux-1.0.so.0
 nux::WindowThread::ProcessForeignEvent(_XEvent*, void*) () from /usr/lib/libnux-1.0.so.0
Title: compiz crashed with SIGSEGV in nux::Area::FindKeyFocusArea()
UpgradeStatus: Upgraded to oneiric on 2011-09-10 (3 days ago)
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare vboxusers

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