firefox-3.5 crashed with signal 5 in _XError()

[userdce]

Binary package hint: firefox-3.5

firefox-3.5

ProblemType: Crash
Architecture: amd64
Date: Thu Jul 23 22:11:29 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/firefox-3.5.1/firefox-3.5
NonfreeKernelModules: nvidia
Package: firefox-3.5 3.5.1+build1+nobinonly-0ubuntu1
ProcCmdline: /usr/lib/firefox-3.5.1/firefox-3.5
ProcEnviron:
 PATH=(custom, user)
 LANG=en_IN
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-3.19-generic
Signal: 5
SourcePackage: firefox-3.5
StacktraceTop:
 ?? () from /usr/lib/libgdk-x11-2.0.so.0
 _XError () from /usr/lib/libX11.so.6
 ?? () from /usr/lib/libX11.so.6
 _XReply () from /usr/lib/libX11.so.6
 XTranslateCoordinates () from /usr/lib/libX11.so.6
Title: firefox-3.5 crashed with signal 5 in _XError()
Uname: Linux 2.6.31-3-generic x86_64
UserGroups: adm admin audio cdrom dialout dip fax fuse lpadmin netdev plugdev sambashare tape vboxusers video

[Vish (vish)]

This error is still present in , Uname: Linux 2.6.31-4-generic i686 , and Package: firefox-3.5 3.5.1+build1+nobinonly-0ubuntu1

[Vlad Brovko (brovka75)]

This error is still present in 2.6.31-4-generic #23-Ubuntu SMP Mon Jul 27 18:39:59 UTC 2009 x86_64 GNU/Linux
and Package: 3.5.1+build1+nobinonly-0ubuntu1

[Vish (vish)]

This happens when apport tries to launch Firefox-3.5 , if not already open.

If firefox-3.5 is already open, Apport is able to connect to launchpad with no problems.

[Ky6uk (ky6uk)]

This bug has affected me.

Firefox: 3.5.2+nobinonly-0ubuntu1
Kernel: 2.6.31-5-generic #24-Ubuntu SMP Sat Aug 1 12:48:18 UTC 2009 i686 GNU/Linux

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