firefox crashed with signal 5 in gdk_x_error()

[Broomer68]

Binary package hint: firefox-3.5

apport trying to open another window/tab for reporting a crash in update-manager, with already 2 tabs openend (unrelated). The new task crashed, the current window with tabs unaffected. And apport this time adds another tab to the running firefox, to report _this_ bug.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Wed Sep 2 12:44:24 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/firefox-3.5.2/firefox
Package: firefox-3.5 3.5.2+nobinonly-0ubuntu2
ProcCmdline: /usr/lib/firefox-3.5.2/firefox https://bugs.launchpad.net/ubuntu/+source/update-manager/+filebug/417Tvf3B3iECzoXXqQjnLCeLaD3?field.title=update-manager+crashed+with+GError+in+__init__%28%29
ProcEnviron:
 LANGUAGE=en_GB.UTF-8
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-8.28-generic
Signal: 5
SourcePackage: firefox-3.5
StacktraceTop:
 gdk_x_error (display=0xb7d0d800, error=0xbff541fc)
 _XError () from /usr/lib/libX11.so.6
 _XReply () from /usr/lib/libX11.so.6
 XGetWindowProperty () from /usr/lib/libX11.so.6
 ?? () from /usr/lib/xulrunner-1.9.1.2/libxul.so
Tags: ubuntu-unr
Title: firefox crashed with signal 5 in gdk_x_error()
Uname: Linux 2.6.31-8-generic i686
UserGroups: adm admin audio cdrom dip fax floppy fuse lpadmin netdev plugdev sambashare scanner tape vboxusers video

[Apport retracing service (apport)]

StacktraceTop:update_direction (keymap_x11=0x170,
_XError (dpy=0xb7d0d800, rep=0xb7d72460)
_XReply (dpy=0xb7d0d800, rep=0xbff54310, extra=0, discard=0)
XGetWindowProperty (dpy=0xb7d0d800, w=90225875,
XRemoteClient::CheckWindow (this=0xbff54518,

[Micah Gersten (micahg)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 411695, so it 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.