firefox crashed with signal 5 in _XError()

Bug #431108 reported by faisal_ct
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
firefox-3.5 (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: firefox-3.5

1

ProblemType: Crash
Architecture: i386
Date: Thu Sep 17 09:09:58 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/firefox-3.5.3/firefox
Package: firefox-3.5 3.5.3+build1+nobinonly-0ubuntu2
ProcCmdline: /usr/lib/firefox-3.5.3/firefox https://launchpad.net/bugs/418300
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-10.34-generic
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.3/libxul.so
Title: firefox crashed with signal 5 in _XError()
Uname: Linux 2.6.31-10-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
faisal_ct (faisal-ct) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

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.3/libxul.so

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-i386-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.