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

[HaruSiga77]

kernel: 3.0.0-6.7
compiz version: 1:0.9.5.0-0ubuntu1
nouveau version: 20091212-0ubuntu1
Weird things happen where shell over lays unity. Think three bars (top n' bottom = gnome; left = unity)

I read on phoronix that unity + compiz + nouveau has issues. Maybe a read of this will help: http://www.phoronix.com/scan.php?page=article&item=linux_desktop_managers1&num=1

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: libnux-1.0-0 1.0.6-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-6.7-generic 3.0.0-rc7
Uname: Linux 3.0.0-6-generic x86_64
Architecture: amd64
Date: Sat Jul 23 10:10:36 2011
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110630)
ProcCmdline: compiz
SegvAnalysis:
 Segfault happened at: 0x7f34f695a418 <_ZN3nux4Area16FindKeyFocusAreaEjmm+24>: mov 0x128(%rax),%rax
 PC (0x7f34f695a418) ok
 source "0x128(%rax)" (0x00000128) 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::FindKeyFocusAreaFrom(nux::NuxEventType, unsigned int, unsigned int, nux::InputArea*, 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::WindowThread::ExecutionLoop(unsigned int) () from /usr/lib/libnux-1.0.so.0
 nux::nux_event_dispatch(_GSource*, int (*)(void*), void*) () from /usr/lib/libnux-1.0.so.0
Title: compiz crashed with SIGSEGV in nux::Area::FindKeyFocusArea()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: admin

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