Closed Bug 467044 Opened 17 years ago Closed 14 years ago

Firefox Minefield won't start after update to Ubuntu Jaunty

Categories

(Firefox :: General, defect)

3.5 Branch
x86
Linux
defect
Not set
critical

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: antonio.mertens, Unassigned)

Details

(Whiteboard: [CLOSEME 2011-2-25])

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.4) Gecko/2008111616 Ubuntu/9.04 (jaunty) Firefox/3.0.4 Build Identifier: http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/firefox-3.1b3pre.en-US.linux-i686.tar.bz2 After upgrading to Ubuntu 9.04 (Jaunty) firefox 3.1 won't start. Running from the terminal firefox-bin executable I get the following error: ./firefox-bin: error while loading shared libraries: libxul.so: cannot open shared object file: No such file or directory I've check and the libxul.so file is in the same directory of the executable. Reproducible: Always Steps to Reproduce: 1. Run ./firefox-bin from terminal (using Ubuntu 9.04 Jaunty) 2. 3. Actual Results: ./firefox-bin: error while loading shared libraries: libxul.so: cannot open shared object file: No such file or directory
Version: unspecified → 3.1 Branch
Try using ./firefox in the directory, rather than firefox-bin
Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode or a fresh profile? If not, please close. These links can help you in your testing. http://support.mozilla.com/kb/Safe+Mode http://support.mozilla.com/kb/Managing+profiles
Whiteboard: [CLOSEME 2011-2-25]
This bug has had the CLOSEME tag for several weeks and the date in the tag is far gone. If the reporter can still see this issue, Please retest with Firefox 3.6.x or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). Then please remove the closeme tag in the whiteboard, mark the bug against the proper version and comment on the bug.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.