I have just installed arch 64 on this machine, and firefox won't open. I can't get any kind of feedback out of the process either. It just sits there, using hardly any cpu, but nothing happens.
ldd /usr/bin/firefox gives me no errors.
This is the output from gdb:
gdb firefox GNU gdb (GDB) 7.5.1 Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-unknown-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/bin/firefox...(no debugging symbols found)...done. (gdb) c The program is not being run. (gdb) run Starting program: /usr/bin/firefox warning: Could not load shared library symbols for linux-vdso.so.1. Do you need "set solib-search-path" or "set sysroot"? [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". Traceback (most recent call last): File "/usr/share/gdb/auto-load/usr/lib/libgobject-2.0.so.0.3400.3-gdb.py", line 9, in <module> from gobject import register File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in <module> import gdb.backtrace ImportError: No module named backtrace [New Thread 0x7fffe87f9700 (LWP 6148)] [New Thread 0x7fffe77df700 (LWP 6149)] [New Thread 0x7fffe6bff700 (LWP 6150)] [New Thread 0x7fffe5de4700 (LWP 6151)] [New Thread 0x7fffe55e3700 (LWP 6152)] [New Thread 0x7fffe49e2700 (LWP 6153)] [New Thread 0x7fffe41e1700 (LWP 6154)] [New Thread 0x7fffe39e0700 (LWP 6155)] [New Thread 0x7fffe2dff700 (LWP 6156)] [New Thread 0x7fffe1e9f700 (LWP 6157)] [New Thread 0x7fffe12ff700 (LWP 6158)] [New Thread 0x7fffe03ff700 (LWP 6159)] [New Thread 0x7fffde1ff700 (LWP 6160)] [New Thread 0x7fffdd9fe700 (LWP 6161)] [New Thread 0x7fffdcbff700 (LWP 6162)] [New Thread 0x7fffdc1ff700 (LWP 6163)] [Thread 0x7fffdcbff700 (LWP 6162) exited] [Thread 0x7fffdc1ff700 (LWP 6163) exited] [New Thread 0x7fffdb9fe700 (LWP 6164)] [New Thread 0x7fffdcbff700 (LWP 6165)] [Thread 0x7fffdcbff700 (LWP 6165) exited] [New Thread 0x7fffdcbff700 (LWP 6166)] [New Thread 0x7fffdc1ff700 (LWP 6167)] [New Thread 0x7fffda48b700 (LWP 6178)] [New Thread 0x7fffd9c8a700 (LWP 6203)] [Thread 0x7fffd9c8a700 (LWP 6203) exited] [Thread 0x7fffe1e9f700 (LWP 6157) exited] [New Thread 0x7fffd9c8a700 (LWP 6239)] [New Thread 0x7fffe1e9f700 (LWP 6240)] [New Thread 0x7fffd9489700 (LWP 6241)] [New Thread 0x7fffd8c88700 (LWP 6242)] [New Thread 0x7fffd8487700 (LWP 6243)] [New Thread 0x7fffd7c86700 (LWP 6244)] [New Thread 0x7fffd7485700 (LWP 6245)] [Thread 0x7fffd7485700 (LWP 6245) exited] [New Thread 0x7fffd7485700 (LWP 6246)] [New Thread 0x7fffd6c84700 (LWP 6247)] [New Thread 0x7fffd6483700 (LWP 6248)] [New Thread 0x7fffd5c82700 (LWP 6249)] [Thread 0x7fffd6c84700 (LWP 6247) exited] [Thread 0x7fffd6483700 (LWP 6248) exited] [New Thread 0x7fffd6c84700 (LWP 6250)] [Thread 0x7fffd6c84700 (LWP 6250) exited] [Thread 0x7fffd7c86700 (LWP 6244) exited]
Then it just sits there forever, spawning and killing new processes. Firefox never appears.
Last edited by rezza (2013-02-12 11:13:14)
Ensure that there is no firefox (or other mozilla) running. Remove (rename) ~/.mozilla. Start firefox from a terminal and see what happens. What goes in the terminal? (run it directely, not through gdb (unless you want to dig in the source code and have not stripped the binaries). Is your system up to date? Is it the official firefox?
firefox -P -no-remote -safe-mode
i totally agree with the guy below.
my hint is only a suggestion if you still have problems after his advice
Last edited by debijan (2013-02-12 16:59:11)
firefox -P -no-remote -safe-mode
In order to test the problem, I think my suggestion is better; at least as a first try. Without Firefox running and without ~/.mozilla; no misconfiguration should prevent Firefox to run. The options you suggest will try to disable any problematic configuration. It can be usefull if you need to start Firefox to fix a configuration problem; but as a firt try renaming the ~/.mozilla is better because you are sure that Firefox can't read anything that can hurt it. Only after having figured out that a bad ~/.mozilla is the cause of the problem, we can try to fix the configuration (or restart with a new configuration).
Last edited by olive (2013-02-12 15:56:15)