compiz crashed with SIGSEGV in CompScreen::insertServerWindow()

[Vlad Golubev]

I want to empty the recycle bin and I pressed the right button of the mouse on the trash icon and chose "Clean". Then opened Firefox (before that I launched it) and window cleaning basket was in the background. then I again pressed right-click on the trash icon and chose "Clean" and Unity crased.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: unity 4.18.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
NonfreeKernelModules: fglrx
ApportVersion: 1.23-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Tue Sep 27 22:30:16 2011
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110915)
ProcCmdline: compiz
SegvAnalysis:
 Segfault happened at: 0x806d081 <_ZN10CompScreen18insertServerWindowEP10CompWindowm+193>: mov 0xc(%eax),%eax
 PC (0x0806d081) ok
 source "0xc(%eax)" (0x00000014) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 CompScreen::insertServerWindow(CompWindow*, unsigned long) ()
 PrivateWindow::reconfigureXWindow(unsigned int, XWindowChanges*) ()
 CompWindow::configureXWindow(unsigned int, XWindowChanges*) ()
 CompWindow::updateAttributes(CompStackingUpdateMode) ()
 PrivateWindow::processMap() ()
Title: compiz crashed with SIGSEGV in CompScreen::insertServerWindow()
UpgradeStatus: Upgraded to oneiric on 2011-09-23 (4 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors: (gnome-settings-daemon:1766): libappindicator-WARNING **: Unable to connect to the Notification Watcher: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.70 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 #857487, 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.