firefox-bin crashed with signal 5 in _XError()

Bug #124893 reported by hawkes
52
This bug affects 11 people
Affects Status Importance Assigned to Milestone
firefox (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: firefox

Tried to open a Java Webstart File

ProblemType: Crash
Architecture: amd64
Date: Mon Jul 9 15:35:50 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/lib/firefox/firefox-bin
NonfreeKernelModules: cdrom
Package: firefox 2.0.0.4+2-0ubuntu3
PackageArchitecture: amd64
ProcCmdline: /usr/lib/firefox/firefox-bin /home/hawkes/Desktop/Vibes.jnlp
ProcCwd: /home/hawkes
ProcEnviron:
 LANGUAGE=de_DE.UTF-8
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: firefox
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
 ?? ()
Title: firefox-bin crashed with signal 5 in _XError()
Uname: Linux ela 2.6.22-7-generic #1 SMP Mon Jun 25 17:07:55 GMT 2007 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip lpadmin plugdev pulse-rt scanner video

Tags: apport-crash
Revision history for this message
hawkes (hawkes) wrote :
Revision history for this message
John Vivirito (gnomefreak) wrote :

Can you please test with firefox 2.0.0.15+1nobinonly-0ubuntu0.7.10 in gutsy to see if it is still reproducible? If so can you please give us a test case (step by step instructions on how to reproduce it. example with files either online or attached but only if it doesnt have personal info of yours. so try with a java file that can be found on net.
Can you please give me versions of java you have installed? I dont see a java plugin installed so its likely you cant open it with webbrowser can you open it if you download the file and open locally?

Changed in firefox:
status: New → Incomplete
Revision history for this message
Marlon Cisternas Milla (mcisternas-deactivatedaccount) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in firefox:
status: Incomplete → Invalid
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.