compiz crashed with SIGSEGV in PluginAdapter::FocusWindowGroup()

[matrinko]

It crashed after opening nautilus

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: libnux-1.0-0 1.10.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Fri Sep 16 14:06:45 2011
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=sk_SK:en
 PATH=(custom, no user)
 LANG=sk_SK.UTF-8
 LC_MESSAGES=sk_SK.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f21109f8f68 <_ZN13PluginAdapter16FocusWindowGroupESt6vectorImSaImEE+504>: mov (%rdi),%rax
 PC (0x7f21109f8f68) ok
 source "(%rdi)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nux
StacktraceTop:
 PluginAdapter::FocusWindowGroup(std::vector<unsigned long, std::allocator<unsigned long> >) () from /usr/lib/compiz/libunityshell.so
 BamfLauncherIcon::Focus() () from /usr/lib/compiz/libunityshell.so
 BamfLauncherIcon::ActivateLauncherIcon(ActionArg) () from /usr/lib/compiz/libunityshell.so
 LauncherIcon::RecvMouseClick(int) () from /usr/lib/compiz/libunityshell.so
 sigc::internal::signal_emit1<void, int, sigc::nil>::emit(sigc::internal::signal_impl*, int const&) () from /usr/lib/compiz/libunityshell.so
Title: compiz crashed with SIGSEGV in PluginAdapter::FocusWindowGroup()
UpgradeStatus: Upgraded to oneiric on 2011-09-16 (0 days ago)
UserGroups: adm admin cdrom dialout 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 #846444, 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.