Land bug 384304 on the 1.8 branch for all non-Firefox/SeaMonkey products

RESOLVED FIXED

Status

()

Core
General
--
major
RESOLVED FIXED
10 years ago
10 years ago

People

(Reporter: reed, Assigned: H. Montoliu)

Tracking

({fixed1.8.1.12})

1.8 Branch
x86
Linux
fixed1.8.1.12
Points:
---
Bug Flags:
blocking1.8.1.12 -

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

10 years ago
Created attachment 296363 [details] [diff] [review]
1.8 branch patch from bug 384304

+++ This bug was initially created as a useless clone of Bug #384304 +++

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.4) Gecko/20061201 Firefox/2.0.0.4 (Ubuntu-feisty)
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.4) Gecko/20070601 Ubuntu/7.10 (gutsy) Firefox/2.0.0.4

If you call firefox through a symlink, e.g. /etc/alternatives/x-www-browser you get the error:

(gutsy_chroot)hjmf@paleo:/$ x-www-browser

run-mozilla.sh: Cannot execute /usr/lib/firefox/x-www-browser-bin.

The link in alternatives is OK:

(gutsy_chroot)hjmf@paleo:/$ ls -l /etc/alternatives/x-www-browser
lrwxrwxrwx 1 root root 16 Jun 11 14:06 /etc/alternatives/x-www-browser -> /usr/bin/firefox

After looking at /usr/bin/firefox script the error seems to be:  in the part that deals with symlinks, seems that somebody missed to pass back the resulting "$progbase" variable to the main process.

Possible patch can be:
--- /usr/bin/firefox	2007-06-13 15:37:26.000000000 +0200
+++ /usr/bin/firefox	2007-06-13 16:23:40.000000000 +0200
@@ -111,6 +111,7 @@
     bn=`basename "$progname"`
     cd `dirname "$progname"`
     progname=`/bin/ls -l "$bn" | sed -e 's/^.* -> //' `
+    progbase=`basename "$progname"`
     if [ ! -x "$progname" ]; then
       break
     fi





Reproducible: Always

Steps to Reproduce:
1. create a symlink to /usr/bin/firefox; e.g. ln -s ./foo /usr/bin/firefox
2. execute the symlink: ./foo
Actual Results:  
the error that raises is:
run-mozilla.sh: Cannot execute /usr/lib/firefox/foo-bin.

Expected Results:  
Should launch the browser as it was meant in the script
Flags: blocking1.8.1.12?
Attachment #296363 - Flags: review+
Attachment #296363 - Flags: approval1.8.1.12?
(Reporter)

Comment 1

10 years ago
This is a blocker for Linux distros. The ones affected by it have already taken the patch themselves, so it's best to get it in our tree to help everybody.
Summary: Land bug 384304 on the 1.8 branch for all non-Firefox products → Land bug 384304 on the 1.8 branch for all non-Firefox products except SeaMonkey
(Reporter)

Updated

10 years ago
Summary: Land bug 384304 on the 1.8 branch for all non-Firefox products except SeaMonkey → Land bug 384304 on the 1.8 branch for all non-Firefox/SeaMonkey products

Comment 2

10 years ago
Just curious: why are you excluding SeaMonkey here?
(Reporter)

Comment 3

10 years ago
(In reply to comment #2)
> Just curious: why are you excluding SeaMonkey here?

Because I already landed the patch for SeaMonkey in bug 384304. :)

Comment 4

10 years ago
ah, sure, thanks. (I obviously approved it myself but got confused as I never actually saw the patch against the xpfe file :)
not blocking
Flags: blocking1.8.1.12? → blocking1.8.1.12-
Comment on attachment 296363 [details] [diff] [review]
1.8 branch patch from bug 384304

approved for 1.8.1.12, a=dveditz for release-drivers
Attachment #296363 - Flags: approval1.8.1.12? → approval1.8.1.12+
(Reporter)

Comment 7

10 years ago
Checking in mail/app/mozilla.in;
/cvsroot/mozilla/mail/app/mozilla.in,v  <--  mozilla.in
new revision: 1.5.4.2; previous revision: 1.5.4.1
done
Checking in calendar/sunbird/app/mozilla.in;
/cvsroot/mozilla/calendar/sunbird/app/mozilla.in,v  <--  mozilla.in
new revision: 1.7.2.4; previous revision: 1.7.2.3
done
Checking in xulrunner/app/mozilla.in;
/cvsroot/mozilla/xulrunner/app/mozilla.in,v  <--  mozilla.in
new revision: 1.2.8.2; previous revision: 1.2.8.1
done
Status: ASSIGNED → RESOLVED
Last Resolved: 10 years ago
Keywords: fixed1.8.1.12
Resolution: --- → FIXED
Reed, can you verify this bug with the RC1 2.0.0.12 build?
You need to log in before you can comment on or make changes to this bug.