compiz crashed with SIGSEGV in CompScreen::insertServerWindow()

[Jack Leigh]

crash when Opera and Gimp were open

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: libnux-1.0-0 1.10.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic-pae 3.0.4
Uname: Linux 3.0.0-11-generic-pae i686
ApportVersion: 1.23-0ubuntu1
Architecture: i386
Date: Fri Sep 23 18:03:03 2011
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
ProcCmdline: compiz
SegvAnalysis:
 Segfault happened at: 0x806d081 <_ZN10CompScreen18insertServerWindowEP10CompWindowm+193>: mov 0xc(%eax),%eax
 PC (0x0806d081) ok
 source "0xc(%eax)" (0x0000026d) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nux
StacktraceTop:
 CompScreen::insertServerWindow(CompWindow*, unsigned long) ()
 PrivateWindow::reconfigureXWindow(unsigned int, XWindowChanges*) ()
 CompWindow::configureXWindow(unsigned int, XWindowChanges*) ()
 CompWindow::raise() ()
 PluginAdapter::FocusWindowGroup(std::vector<unsigned long, std::allocator<unsigned long> >) () from /usr/lib/compiz/libunityshell.so
Title: compiz crashed with SIGSEGV in CompScreen::insertServerWindow()
UpgradeStatus: Upgraded to oneiric on 2011-09-22 (1 days ago)
UserGroups:

XsessionErrors:
 (gimp-2.6:2764): GLib-WARNING **: /build/buildd/glib2.0-2.29.92/./glib/goption.c:2168: ignoring no-arg, optional-arg or filename flags (8) on option of type 0
 (gnome-settings-daemon:2410): libappindicator-WARNING **: Unable to connect to the Notification Watcher: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.87 was not provided by any .service files

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