184299 - Mozilla won't startup

Status: VERIFIED DUPLICATE of bug 183849

(SeaMonkey :: General, defect)

Description

[David Castro]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)
Build Identifier: http://ftp.mozilla.org/pub/mozilla/releases/mozilla1.2.1/mozilla-win32-1.2.1-installer.exe

Mozilla 1.0.1 has worked just fine for a long time, but I have upgraded to 
1.2.1 and things are now broken.  It will load the browser right after the 
install is completed, but once closed it will not start again (not even after 
restart).  It loads the mozilla splash screen and just hangs.  Under the task 
manager it maintains a total CPU time of 1 second as if it is blocking for 
something.

It may be important to note that I have not enabled the quick launch feature.

Reproducible: Always

Steps to Reproduce:
1. Install mozilla 1.2.1
2. Close mozilla
3. Try to reopen mozilla

Actual Results:  
Hangs at the splash screen

Expected Results:  
Load properly of course ;)

Stock, fully upgraded win2k box.  Everything else works fine...no other 
applications are encountering abnormal problems.

I am willing to run any tracing programs on Mozilla to get more information on 
the nature of the crash...if you have any suggestions as to what would be 
useful for you all.  I would send an strace if it was broken in Linux, not 
quite sure about what is best for Windows though.

Comment 1

[Boris Zbarsky [:bzbarsky]]

jrgm, is this your fastload hang striking again?

Comment 2

[John Morrison]

Yes, this sounds like bug 183849 (assuming you have only one profile; if you 
have two profiles, you should be able to get as far as the profilemanager
dialog, but will hang when you select your profile and proceed from there).

Try looking in <profileDirectory>/chrome/chrome.rdf and look for a set of 
lines that look like:
  <RDF:Description about="urn:mozilla:package:chatzilla">
    <c:selectedSkin resource="urn:mozilla:skin:modern/1.0:chatzilla"/>
  </RDF:Description>

If the selectedSkin says something other than '...skin:modern/1.0:...' then
edit that file and make it say 'modern/1.0'. If that fixes your problem, then
mark this as a duplicate of bug 183849.

(And as bz noted in email, "quick launch" != "fastload". 'fastload' is an 
implementation detail that most users will not know about. It involves storing
[and then re-loading at startup] a serialized form of the XUL and Javascript 
on disk.

Comment 3

[David Castro]

*** This bug has been marked as a duplicate of 183849 ***

Comment 4

[Helge Moulding]

Are you all sure this is the same as 183849? I've got the same problem. I never 
use profiles. The problem went away when I enabled the "Quick Launch" feature
during installation. My system runs Windows ME, but otherwise the problem
seems to be identical to what the original report indicated.

As far as themes are concerned, I did notice that installing 1.2.1 made my "Wood" 
theme go away. I still haven't figured out what might have done that: the theme 
file still seems to be in my chrome folder, but the theme doesn't appear in the 
theme list. Switching themes between Classic and Modern doesn't seem to make any
difference to the operation of Mozilla.

Comment 5

[John Morrison]

v