Red Hat Bugzilla – Bug 109594
Cannot run Mozilla
Last modified: 2007-11-30 17:10:33 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.79 [en] (X11; U; Linux 2.4.20-20.9 i686)
Description of problem:
Cannot run Mozilla.
If launched from KDE menu, cursor blinks for some time but nothing
When typed "mozilla" in command prompt got return to shell in about 2
seconds, without any messages.
When started with "mozilla -v" the message:
Mozilla 1.4.1, Copyright (c) 2003 mozilla.org, build 2003103016
so the mozilla is there
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Actual Results: nothing
Expected Results: mozilla window appearing
May be caused by setting locale to Polish.
I had this same problem after upgrading from redhat9. Deleting the
java plug-in (or symlink to it) from /usr/lib/mozilla/plugins fixed it
Please see bug 108719.
To start mozilla in your locale just comment out lines 183,184 and 185
in /usr/bin/mozilla. It's interim measure but it's must help.
Lines (mozilla 1.4.1-15):
# check system locale
MOZLOCALE=`echo $LANG | sed "s|_\([^.]*\).*|-\1|g"`
[ -f $MOZILLA_FIVE_HOME/chrome/$MOZLOCALE.jar ] && MOZARGS="-UILocale
This seems to address two different issues: the locale issue and the
Java plugin issue - just like Rasmus (comment #1) Mozilla crashed on
me after upgrading from RHL9 to FC1. Turns out that the Java plugin
link pointed to the wrong version of the JRE - I had installed Sun's
J2SDK 1.4.2, but the symlink didn't point to the plugin that was
compiled with GCC 3.2 (strangely enough it was the other one that
worked for me under RHL9, that's why I had done it like this). After
changing the symlink to the Java plugin in the 'ns610-gcc32' directory
Mozilla works and Java applets seem fine as well.
The 'bug' in Mozilla simply seems to be that a plugin that dies can
take down the browser without any indication of what happened. Of
course, it would be best if a non-functional plugin just stayed dead,
but if it can at least be caught that would be useful for troubleshooting.
Unfortunately, we can't fix that in the plugin since it's not open source.