firefox-3.5 crashed with signal 5 in _XError()

[Krzysztof Klimonda]

Binary package hint: firefox-3.5

I was trying to report an apport crash in another application..

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Sat Aug 8 13:40:01 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/firefox-3.5.2/firefox-3.5
NonfreeKernelModules: nvidia
Package: firefox-3.5 3.5.2+nobinonly-0ubuntu1
ProcCmdline: /usr/lib/firefox-3.5.2/firefox-3.5 https://bugs.launchpad.net/ubuntu/+source/gwibber/+filebug/mDoYUxS9Zu2eLvfWERIeO7m1buj?field.title=gwibber+crashed+with+AttributeError+in+load_messages%28%29
ProcEnviron:
 LANGUAGE=en_GB.UTF-8
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-5.24-generic-pae
Signal: 5
SourcePackage: firefox-3.5
StacktraceTop:
 ?? () from /usr/lib/libgdk-x11-2.0.so.0
 _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
Title: firefox-3.5 crashed with signal 5 in _XError()
Uname: Linux 2.6.31-5-generic-pae i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:_gdk_windowing_exit ()
?? ()
_XError (dpy=0xb790d800, rep=0x504)
_XReply (dpy=0xb790d800, rep=0xbfb47470, extra=0, discard=0)
XGetWindowProperty (dpy=0xb790d800, w=100663299,

[Boniek (boniek12p)]

this error happens when trying to send bug report while havin firefox opened

[Hellsgator (hellsgate)]

same here. Ubuntu is unable to open firefox trying to send bug reports.

[Micah Gersten (micahg)]

@kklimonda

Could you please try to duplicate this with the latest GTK libs? 2.17.7 was released since you submitted this.

[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 401055, 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.