Closed Bug 80831 Opened 24 years ago Closed 24 years ago

mozilla 0.9 freezes on startup on linux

Categories

(SeaMonkey :: General, defect)

x86
Linux
defect
Not set
critical

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: jks, Assigned: asa)

Details

(Keywords: hang)

From Bugzilla Helper: User-Agent: Mozilla/4.76 [en] (X11; U; Linux 2.2.15 i686) BuildID: ??? [jks@d1 /usr/local/mozilla] ./mozilla ./run-mozilla.sh ./mozilla-bin MOZILLA_FIVE_HOME=/local/move/usr/local/mozilla0.9 LD_LIBRARY_PATH=/local/move/usr/local/mozilla0.9:/local/move/usr/local/mozilla0.9/plugins:/usr/local/pgsql/lib LIBRARY_PATH=/local/move/usr/local/mozilla0.9:/local/move/usr/local/mozilla0.9/components SHLIB_PATH=/local/move/usr/local/mozilla0.9 LIBPATH=/local/move/usr/local/mozilla0.9 ADDON_PATH=/local/move/usr/local/mozilla0.9 MOZ_PROGRAM=./mozilla-bin MOZ_TOOLKIT= moz_debug=0 moz_debugger= <freezes here, no window pops up, prompt doesn't return.> Reproducible: Always Steps to Reproduce: 1. Cd to the mozilla directory and run ./mozilla 2. 3. Actual Results: Nothing. Expected Results: A mozilla window should pop up. I have run Mozilla 0.8.1 on this system. I tried to search for this bug using netscape but I didn't find it before netscape crashed on me. This is a redhat 6.x system.
Did you install the Flash plugin before starting Mozilla? If so, is your sound device busy when mozilla hangs? Also, did you install on top of 0.8.1 or did you do a clean install?
Comments from reporter: Sorry for not replying via bugzilla. As a matter of fact I did copy the flash plugin from my 0.8.1 install to where I installed mozilla 0.9 but I took it out when mozilla wouldn't start and mozilla still didn't start. I didn't copy over 0.8.1 and 0.8.1 still starts. My sound device was not busy (afaik).
Severity: blocker → critical
jks, have you tried deleting your ~/.mozilla directory? Sometimes a new version won't install with cruft from an older version in that directory. You will lose your bookmarks, etc. though.
OK I moved my .mozilla directory and now instead of just freezing I get a command prompt back: [jks@d1 /local/move/usr/local/mozilla0.9] ./mozilla ./run-mozilla.sh ./mozilla-bin MOZILLA_FIVE_HOME=/local/move/usr/local/mozilla0.9 LD_LIBRARY_PATH=/local/move/usr/local/mozilla0.9:/local/move/usr/local/mozilla0.9/plugins:/usr/local/pgsql/lib LIBRARY_PATH=/local/move/usr/local/mozilla0.9:/local/move/usr/local/mozilla0.9/components SHLIB_PATH=/local/move/usr/local/mozilla0.9 LIBPATH=/local/move/usr/local/mozilla0.9 ADDON_PATH=/local/move/usr/local/mozilla0.9 MOZ_PROGRAM=./mozilla-bin MOZ_TOOLKIT= moz_debug=0 moz_debugger= [jks@d1 /local/move/usr/local/mozilla0.9]
Keywords: hang
Worksforme with 061208 mozilla linux build on RedHat 6.2
I just tried mozilla 0.9.1. I removed my .mozilla directory [jks@d1 /local/move/usr/local/mozilla0.9.1] ./mozilla ./run-mozilla.sh ./mozilla-bin MOZILLA_FIVE_HOME=/local/move/usr/local/mozilla0.9.1 LD_LIBRARY_PATH=/local/move/usr/local/mozilla0.9.1:/local/move/usr/local/mozilla0.9.1/plugins:/usr/local/pgsql/lib LIBRARY_PATH=/local/move/usr/local/mozilla0.9.1:/local/move/usr/local/mozilla0.9.1/components SHLIB_PATH=/local/move/usr/local/mozilla0.9.1 LIBPATH=/local/move/usr/local/mozilla0.9.1 ADDON_PATH=/local/move/usr/local/mozilla0.9.1 MOZ_PROGRAM=./mozilla-bin MOZ_TOOLKIT= moz_debug=0 moz_debugger= [jks@d1 /local/move/usr/local/mozilla0.9.1] I got a prompt back, but mozilla didn't work.
R.K.Aa do you have any ideas here?
Reporter: Does it start when you start it as root? If it does: While you have it running as root, start all installed components once as well (mailnews, composer). No need to created mail-accounts. Then quit mozilla and try start it as a regular user. If starting it as root doesn't work: Does it start for user root if you remove the flash plugin first?
That did it. I started it as root then I could start it as my regular user account. But there appears to be no flash plugin distributed with mozilla.
Good you got it going :) There is no flash distributed along with mozilla, but if you have it installed from before in nc4.7* you just copy the bits you need (as root) with for instance cp /usr/local/netscape/plugins/*lash* /local/move/usr/local/mozilla0.9.1/plugins Otherwise download from macromedia's flash site and install according to instructions. Resolving as "works for me" per reporters comment.
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
ahh.. and the reason i asked about flash was a known bug where moz won't start if /dev/dsp is busy and flash *is* installed. (Like if you have xmms running while starting moz etc.)
I'm not sure this should be marked as resolved. Should you be able to run this as a user right after root untars the installation? Or if not should you at least get a message 'this must be run once as root' ?
There should be a release note about this. For additional information see bug 42184, bug 49345, bug 45863.
> Should you be able to run this as a user right after root untars the > installation? No. Please read the release notes (I'd say which section, but I can't access www.mozilla.org at the moment). Simply untarring does not install the product properly.
something like ./mozilla ./regxpcom && ./mozilla ./regchrome should work w/o requiring you to be root, some day the relnotes will have good instructions for doing this.
Status: RESOLVED → VERIFIED
I just looked at my mozilla 0.9.1 directory and apparently the release notes aren't in the tarball.
The Release Notes are linked to under the "Help" item on menubar. The need for a README file is, amongst others, covered in bug bug 45863.
Yeah.. The only notes are on the web. From http://mozilla.org/releases/mozilla0.9.1/#install, in the Linux section: You must run Mozilla at least once to complete autoregistration and for the component.reg file to be written to the installation directory. If a different user (other than the person who installed the product) runs the program first, a core dump will occur. (Bug 49345) Yes, that's a weird requirement for a Linux software package. The RPM and .deb distributions avoid this requirement by starting out with things autoregistered, I believe (they may do the registration as part of post-inst).
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.