Ubuntu
firefox-3.5 package

firefox crashed with signal 5 in gdk_x_error()

Bug #434179 reported by Matt Walker on 2009-09-21

This bug report is a duplicate of: Bug #427799: firefox crashed with signal 5 in gdk_x_error(). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	firefox-3.5 (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: firefox-3.5

It crashed when xserver crashed on my computer.

ProblemType: Crash
Architecture: i386
CheckboxSubmission: 1357e3ee17131bd82a54689439059754
CheckboxSystem: 4d87cc8055778f13120efdb72bd81ff6
CrashCounter: 1
Date: Mon Sep 21 11:06:42 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/firefox-3.5.3/firefox
NonfreeKernelModules: nvidia
Package: firefox-3.5 3.5.3+build1+nobinonly-0ubuntu2
ProcCmdline: /usr/lib/firefox-3.5.3/firefox http://www.facebook.com/n/?profile.php&id=10723727&aref=55095523
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-10.34-generic
Signal: 5
SourcePackage: firefox-3.5
StacktraceTop:
gdk_x_error (display=0xb7c0d800, error=0xbf8cf40c)
_XError (dpy=0xb7c0d800, rep=0xb7c72460)
_XReply (dpy=0xb7c0d800, rep=0xbf8cf520, extra=0, discard=0)
XGetWindowProperty (dpy=0xb7c0d800, w=4293338,
?? () from /usr/lib/xulrunner-1.9.1.3/libxul.so
Title: firefox crashed with signal 5 in gdk_x_error()
Uname: Linux 2.6.31-10-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

Matt Walker (matthaeus123) wrote on 2009-09-21:

ExtensionSummary.txt Edit (929 bytes, text/plain; charset="utf-8")
profile_default_pluginreg.dat.txt Edit (2.8 KiB, text/plain; charset="utf-8")
profiles.ini.txt Edit (94 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2009-09-21: This bug is a duplicate

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