Closed Bug 191472 Opened 22 years ago Closed 19 years ago

Setting MOZILLA_FIVE_HOME causes browser not to start

Categories

(SeaMonkey :: General, defect)

x86
Linux
defect
Not set
major

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 202985

People

(Reporter: chabotc, Assigned: asa)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3b) Gecko/20030131
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3b) Gecko/20030131

I have just finished compiling a recent nightly/expirimental/gtk2 mozilla (from
src.rpm setting the compiler to 'normal' gcc 3 (on rh8)) and when i try to run
mozilla, it instantly crashes.

If i remove the 'export MOZILLA_FIVE_HOME..' from the /usr/bin/mozilla script,
the browser starts up as normal again; Seemingly fully functional.

I have seen this behaviour in all mozilla compiles i have tried in the last 10
days or so (last one that worked 'normally' was from < 2003-01-17). I have in
the period seen the same behaviour with gtk2 builds i have done from a CVS tree,
so i think the problem does not exist only in the expirimental/gtk2 src.rpm's



Reproducible: Always

Steps to Reproduce:
Summary: Setting MOZILLA_FIVE_HOME causes browser not to start → Setting MOZILLA_FIVE_HOME causes browser not to start
I can confirm that it happens on the following builds.
2003020419
2003012512
2003012317

If I remove the export MOZILLA_FIVE_HOME line from the script, Mozilla starts
and is seeming normal.
A follow up to my previous comment...  The last build that worked properly for
me was 2003011416.  I have not done every nightly but it seems to have started
just after the 14th of January.
I think the answer will be "don't set it" see 202985 comment #4
Product: Browser → Seamonkey

*** This bug has been marked as a duplicate of 202985 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.