firefox-3.5 crashed with signal 5 in _XError()

Bug #406066 reported by gadLinux
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
firefox-3.5 (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: firefox-3.5

Ubuntu crashed while showing one page that takes long to open and you start to close other tabs...

This failed for me but not test case can be provided.

thank you

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Wed Jul 29 00:48:20 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=es_ES.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.30-9.10-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.30-9-generic x86_64
UserGroups: adm admin cdrom dialout games libvirtd lpadmin mldonkey plugdev sambashare tomcat6 vboxusers video

Revision history for this message
gadLinux (gad-aguilardelgado) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:gdk_x_error (display=<value optimized out>,
_XError (dpy=0x7f109acb1000, rep=0x7f107caff520)
process_responses (dpy=0x7f109acb1000,
_XSend (dpy=0x7f109acb1000,
?? ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in firefox-3.5 (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Micah Gersten (micahg) wrote :

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.

visibility: private → public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.