Red Hat Bugzilla – Bug 358611
Firefox fails to launch
Last modified: 2008-04-09 10:05:01 EDT
Description of problem:
Firefox fails to launch, either from the menus or the command line.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install Fedora x86_64 from live cd.
2. Try to launch default Firefox
Firefox window does not appear. Attempts to launch Firefox after this result in
it reporting that another instance of Firefox is running but not responding, and
to close the current session.
Checking System Monitor reveals that Firefox.bin and Firefox are indeed both
running, but no window is shown.
Launching Firefox from the command line also seems to not report anything,
rather it just hangs there.
Firefox to launch normally.
Any more info needed? I'll provide what I can...
I'm also getting this on one of our systems, also x86_64 (no 32 bit firefox
The weird thing is that on one account it works, but on another it doesn't.
I've cleaned out the profile (rm -r ~/.*), removed and reinstalled firefox and
done an selinux relabel but it still won't launch.
If I launch firefox with a URL as an argument then I get a firefox window
appearing, but it's immediately non-responsive and I have to kill it.
I've got an strace of the session where it fails which I'll attach.
This is using the latest firefox-18.104.22.168-3.fc8
Created attachment 294658 [details]
strace log of a firefox session which hangs
Thanks for the bug report. We have reviewed the information you have provided
above, and there is some additional information we require that will be helpful
in our diagnosis of this issue.
Please install firefox-debuginfo; in order to do this you have to enable
yum install --enablerepo=\*debuginfo firefox-debuginfo
(if you use x86_64 firefox, install firefox-debuginfo.x86_64 package).
Then run firefox with a parameter -g. That will start firefox running inside of
gdb debugger. Then use command run and do whatever you did to make firefox
crash. When it happens, you should go back to the gdb and run
(gdb) thread apply all backtrace
This produces usually many screens of the text. Copy all of them into a text
editor and attach the file to the bug as an uncompressed attachment.
We will review this issue again once you've had a chance to attach this information.
Thanks in advance.
Created attachment 294761 [details]
gdb trace of hanging firefox session
I'm not sure that this is much use since firefox doesn't actually crash - it
The attached gdb session is from where I launched firefox with a URL as an
argument, which opens a window which is non-responsive. Gnome then prompts me
to kill it, which is where the SIGKILL comes from.
Since bugzilla doesn't let you move bugs out of NEEDINFO when adding an
attachment I'm just using this to change the bug state.
Created attachment 294763 [details]
gdb trace of hanging firefox session
I forgot to add the stack trace to the last attachment. This one is
interrupted where it hangs and has a stack trace applied.
At this point, we're going to only be taking security fixes and major stability
fixes into this release of Fedora. However, we still want to ensure the bug is
fixed in the next version. We'd appreciate if you could test Firefox 3,
available at http://www.mozilla.com/en-US/firefox/all-beta.html or now shipping
as the default in Fedora rawhide and provide feedback as to whether it still
exists so we can file a ticket upstream to try to fix it in Firefox 3 before it
Since there are insufficient details provided in this report for us to
investigate the issue further, and we have not received feedback to the
information we have requested above, we will assume the problem was not
reproducible, or has been fixed in one of the updates we have released for the
Users who have experienced this problem are encouraged to upgrade to the latest
update of their distribution, and if this issue turns out to still be
reproducible in the latest update, please reopen this bug with additional
Closing as INSUFFICIENT_DATA.
[This is a mass-closing request, if you think that this bug shouldn't be closed,
please, reopen with additional information.]