Closed Bug 57538 Opened 24 years ago Closed 24 years ago

M18 does not run at all (crashes at start)

Categories

(SeaMonkey :: Installer, defect, P3)

x86
Linux
defect

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 41057

People

(Reporter: mmarkov, Assigned: ssu0262)

Details

M18 always crashes at start. Tried both precompiled binaries and binaries compiled here, same result. OS is Linux, kernel 2.2.15, glibc 2.1.3, X 3.3.6, running KDE 2.0rc2, and having gtk 1.2.8 Output of ./mozilla (trying to run it in $MOZILLA_FIVE_HOME): ./run-mozilla.sh ./mozilla-bin MOZILLA_FIVE_HOME=. LD_LIBRARY_PATH=.:/usr/lib:/usr/local/lib:/usr/local/kde/lib: /usr/local/qt/lib:/usr/local/pack/mozilla LIBRARY_PATH=.:./components:/usr/lib:/usr/local/lib: /usr/local/kde/lib:/usr/local/qt/lib SHLIB_PATH=. LIBPATH=. ADDON_PATH=. MOZ_PROGRAM=./mozilla-bin MOZ_TOOLKIT= moz_debug=0 moz_debugger= After this output nothing happens, it just exits without any error message or core dump. If I try to start directly ./mozilla-bin (all environm. var's set correctly), it crashes with the message: Segmentation fault There is no core dump. I suspect that the code which causes the segmentation fault is in libgkgfx.so If I don't set manually LD_LIBRARY_PATH to include /usr/local/pack/mozilla (my MOZILLA_FIVE_HOME dir), mozilla-bin exits with the message "Cannot load libgkdfx.so" or so, which means that this shared lib is the first one to be loaded, and then, or after that, the crash happens. I was advised to remove any user profile I have. I did so, removing the directory ~/.mozilla Still I cannot start Mozilla. When ~/.mozilla is removed, then mozilla-bin creates it again before crashing. This means that it gets past the point when this directory is created. Thanks. Minko Markov Victoria, British Columbia, Canada
If you install to a directory as root, and one that only root has write access to, you MUST start mozilla as user root once, before normal users can start it. Perhaps this is the error you encounter?
Minko, see bug 41057 and bug 42184 that R.K.A.a is referring to. Is this the problem you are experiencing?
The above comments (on 2000-10-21 16:46 and on 2000-10-22 14:44) are correct. Indeed M18 (Linux) needs write permissions on the directory where the binaries reside *during the first run*. And the problem has already been described, e.g. bug report 41057. It is a bug, because it is normal to have the directory $MOZILLA_FIVE_HOME root-only-writable and avoid running a browser as a root at the same time. Further, there is no error message after the failed write. *** This bug has been marked as a duplicate of 41057 ***
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Verified dup
Status: RESOLVED → VERIFIED
QA Contact: bugzilla → ktrina
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.