mozilla script should sanity check MOZILLA_FIVE_HOME

RESOLVED INCOMPLETE

Status

()

Core
Build Config
RESOLVED INCOMPLETE
15 years ago
9 months ago

People

(Reporter: mjbjr, Unassigned)

Tracking

Trunk
x86
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

15 years ago
User-Agent:       Opera/6.12 (Linux 2.4.20 i686; U)  [en]
Build Identifier: http://mozilla.org/

installing, as 'root', 'mozilla-i686-pc-linux-gnu-1.3-sea.tar.gz'

installation goes fine, and I accept the defaults.  'mozilla' automatically starts at the end of the installation.  Close it.

still as 'root'.  Try first post-install startup...

cd to moz install dir, '/usr/local/mozilla', run './mozilla', returns:

localhost mozilla # ./mozilla
./mozilla: line 120: /usr/lib/mozilla/run-mozilla.sh: No such file or directory
./mozilla: line 120: exec: /usr/lib/mozilla/run-mozilla.sh: cannot execute: No such file or directory

It's looking in the wrong dir for 'run-mozilla.sh', it's in the install dir: '/usr/local/mozilla', NOT
/usr/lib/mozilla/.

I've installed twice, and the same exact thing happens.


Reproducible: Always

Steps to Reproduce:

1.
2.
3.

Actual Results:  
mozilla doesn't start

Expected Results:  
mozilla should have started.

Comment 1

15 years ago
do you have MOZILLA_FIVE_HOME set?  if you do unset it.
if that doesn't help do
sh -x ./mozilla
(Reporter)

Comment 2

15 years ago
Andrew Schultz nailed it...
Additional Comment #1 From Andrew Schultz 2003-04-22 18:39
do you have MOZILLA_FIVE_HOME set?

that was the problem.  It was left over from a previous install, and
was set to '/usr/lib/mozilla'.

I'm not going to change the bug to 'FIXED', even if (?) I can, because the startup script(s)
should have detected that 'run-mozilla.sh' was in the current dir, the default install dir.

Hopefully, the powers that be will fix this.

Comment 3

15 years ago
this bug would not be FIXED because no patch was checked in to FIX it.
not critical

dunno if this is even a good idea (users at least need a way to know
MOZILLA_FIVE_HOME is screwed up)
marking NEW anyway and resummarizing

==> Build Config
Assignee: asa → seawood
Severity: critical → normal
Status: UNCONFIRMED → NEW
Component: Browser-General → Build Config
Ever confirmed: true
QA Contact: asa → granrose
Summary: mozilla-1.3 can't find run-mozilla.sh → mozilla script should sanity check MOZILLA_FIVE_HOME
I'm really sick of these bugs.  Users should not be setting MOZILLA_FIVE_HOME
unless they know what they're doing.  I'm very tempted to just make the script
exit with an error if MOZILLA_FIVE_HOME is set at all.

Comment 5

15 years ago
Is there a reason the script still honors MOZILLA_FIVE_HOME (other than
history)?  With soft-link backtracking, it doesn't seem useful for the startup
script.
Mass reassign of Build/Config bugs to Leaf.
Assignee: netscape → leaf

Updated

13 years ago
Assignee: leaf → cmp
Product: Browser → Seamonkey

Comment 7

13 years ago
*** Bug 191472 has been marked as a duplicate of this bug. ***

Comment 8

12 years ago
Mass reassign of open bugs for chase@mozilla.org to build@mozilla-org.bugs.
Assignee: chase → build

Updated

12 years ago
Assignee: build → nobody
Component: Build Config → Build Config
Product: Mozilla Application Suite → Core
QA Contact: granrosebugs → build-config

Comment 9

11 years ago
(In reply to comment #4)
> exit with an error if MOZILLA_FIVE_HOME is set at all.
if you clink on a link in thunderbird and it would start firefox, then the firefox launch-script will inherit the thunderbird environment. This environment unfortunately has MOZILLA_FIVE_HOME set even though the user did not set it. This can actually prevent firefox from starting up (it does not work in my case, I am investigating whether I have to file a bugreport to mozilla or debian for that)

Comment 10

9 months ago
Mass bug cleanup for Core:Build Config.

If you feel this bug has been closed in error, please re-open with new details.
Status: NEW → RESOLVED
Last Resolved: 9 months ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.