Closed Bug 95900 Opened 24 years ago Closed 24 years ago

Browser did not start

Categories

(SeaMonkey :: General, defect)

x86
Linux
defect
Not set
major

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 76033

People

(Reporter: baeda, Assigned: asa)

Details

Attachments

(1 file)

All officel release since 0.9.1 and all own build from cvs All common hints did not correct this behavoir (rm -r ~/.mozilla, start as root first time). After creation of a profile, the browser window does not appear. Here is the output of the second start: >cd mozilla >./mozilla ./run-mozilla.sh ./mozilla-bin MOZILLA_FIVE_HOME=/home/software/mozilla LD_LIBRARY_PATH=/home/software/mozilla:/home/software/mozilla/plugins LIBRARY_PATH=/home/software/mozilla:/home/software/mozilla/components SHLIB_PATH=/home/software/mozilla LIBPATH=/home/software/mozilla ADDON_PATH=/home/software/mozilla MOZ_PROGRAM=./mozilla-bin MOZ_TOOLKIT= moz_debug=0 moz_debugger= Type Manifest File: /home/software/mozilla/components/xpti.dat nsNativeComponentLoader: autoregistering begins. nsNativeComponentLoader: autoregistering succeeded nNCL: registering deferred (0) Unable to enumerator app shell components, GetSubtree rv=0x80510003 GFX: dpi=90 t2p=0,0625 p2t=16 depth=24 WEBSHELL+ = 1 How can i give you more information about this behavoir. Can you give me detailed information to trace down the problem ? How can I generate a proper output, to give you more information about what´s going on ?
did you also remove your old mozilla install before replacing it?
1. You mentioned you're doing your own builds. What is your configure line? 2. Are you building with qt? (bug 76033) 3. If #2 didn't help, try setting NSPR_LOG_MODULES=all:5 (as an environment variable) before running mozilla. This will dump a ton of stuff on screen so be prepared :) This stuff will probably help pinpoint it further. If you do run it, please attach it rather than post it as a comment. it's quite huge and an attachment will make reading this bug easier than having to scroll for miles. But I have a suspicion that this is a dupe of bug 76033...
Yes, i removed all my installations, since none of them was working. 1.) I tried a lot of configuration option. The most common way afer make distclean is make -f client.mk as delivered from the cvs. But the builds from www.mozilla.org show the behavoir described above. Fresh cvs co behave the same way. 2.) building as described in #76033 is goin on. 3.) The output is attached (46372) Last output occured in security/manager/ssl/src/nsNSSComponent.cpp
OK, you are right. It is #76033 ! ./configure --with-x did the job! Where can I find the recommended, always working, configure options ? What options can be toggled without known bugs ? Why does the default make -f client.mk show this kind of behavior ? Thanks for pointing me to #76033 *** This bug has been marked as a duplicate of 76033 ***
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
config options: http://webtools.mozilla.org/build/config.cgi the ones listed with checkbox should work in general (unless clearly stated otherwise)
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: