seen on commercial and mozilla build 2002-03-05-08-trunk install and attempt to run the build but it won't launch. seeing the following in the terminal window: Gtk-CRITICAL **: file gtkmain.c: line 534 (gtk_main_quit): assertion `main_loops != NULL' failed. /usr/local/mozilla/mozilla: /tmp/xpizjiQvY/bin/run-mozilla.sh: No such file or directory exec: /tmp/xpizjiQvY/bin/run-mozilla.sh: cannot execute: No such file or directory > cd /usr/local/mozilla/ > ls chrome liblber40.so libsmime3.so regExport components libldap40.so libsoftokn3.so regchrome defaults libmozjs.so libssl3.so registry icons libmozz.so libxlibrgb.so regxpcom install.log libmsgbaseutil.so libxpcom.so res libgkgfx.so libnspr4.so libxpistub.so run-mozilla.sh libgtkembedmoz.so libnss3.so mozilla searchplugins libgtksuperwin.so libnssckbi.so mozilla-bin xpicleanup libgtkxtbin.so libplc4.so mozilla-xremote-client libjsj.so libplds4.so plugins >

might be related to bug 57866

twalker: is this still happening to you now? Bug 57866 had caused an infinite loop in the mozilla launch script which was resolved now...

aki is running a respin now. when it is complete I'll check to see if it is fixed.

Seen on linux redhat 6.2 (Commercial build: 2002-03-05-09-trunk) using the installer. During the installation, the Error dialog pops up saying "Fatal error[-613]: couldn't creat the directory".

still seeing this on the respin 2002-03-05-11-trunk

I see it after install, but runs from the command line now.

this may be worth mentioning: If I cd to the default location of the installation and attempt to run this by hand with ./run-mozilla netscape, it launches the version of Netscape 4.x installed on the machine.

ah yes, but running just ./netscape works. the build launches. I was told that running through the script was more reliable. Heh? anyway, reducing to critical and removing smoketest keyword.

is this bug 57866?

I'm not sure if it is. I'm not sure where it's getting the /tmp path in the first place, and when I do a ./run-mozilla.sh mozilla in build 2002030511, I get ./run-mozilla.sh: line 72: 19712 Segmentation fault $prog ${1+"$@"} ./run-mozilla.sh and ./mozilla work, but the launch after the install breaks with the same /tmp/xxxxxxxx/bin/run-mozilla.sh error. The error in Comment #4 just seems like a permissions problem?

was there any changes made in the run-mozilla.sh script. If we don't use it, we can run the app. using the script gives the directory misdirection errors.

ah, nevermind, ./run-mozilla.sh ./mozilla fixes that error. was calling a different version of mozilla =P So we just have the install launch broken now.

Proper fix has been checked in.

Chris, was the fixed checked in on time to make this morning build? This bug is still present on linux commercial 2002-03-06-07-trunk.

ah, wait a sec....it has to be "./run-mozilla.sh ./mozilla" not "./run-mozilla.sh mozilla". The former works for me...the later does not. marking verified.

i always thought you were supposed to do ./mozilla or ./run-mozilla.sh ./mozilla-bin

wait a minute. The build is failing to launch from the installer with the errors mentioned in the initial bug description. I can however run the build by hand after that. I'm still testing (and retesting/installing) the 2002-03-06-07-trunk build. based on the post time when seawood said he checked the fix in, i believe it was picked up in this build. reopening. I'm sorry about my confusion in verifying this.

Argh. My bad. I fixed the symptons (eternal loop) but I missed the actual problem. The mozilla script now honors MOZILLA_FIVE_HOME. However, since the mozilla-installer script also sets MOZILLA_FIVE_HOME, the mozilla script tries to exec run-mozilla.sh from the wrong place.

Syd said that the installer binary doesn't use MOZILLA_FIVE_HOME at all and that he suspects that it was only set for the sake of the mozilla app. Since mozilla handles that now, don't bother setting it in the installer script.

The patch has been checked in.

still failing to launch from install on linux commercial build 2002-06-07-08-trunk

marking fixed, 'cause this looks good now on as seen on linux commercial build 2002-03-08-07-trunk

Comment on attachment 72933 [details] [diff] [review] Do not set MOZILLA_FIVE_HOME in installer script can we get approval before checking in next time? thanks. a=asa (on behalf of drivers) for checkin to the 1.0 trunk Also, does this need to land on the branch or is it trunk-only?

Trunk only. The symlink patch was backed out on the branch.