Closed Bug 176118 Opened 22 years ago Closed 22 years ago

launch freezes at splash screen / creating first window message

Categories

(Core Graveyard :: Skinability, defect)

Product:
Core Graveyard
Component:
Skinability
Platform:
PowerPC
macOS
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 144027

People

(Reporter: klanda, Assigned: asa)

References

Details

User-Agent:       Mozilla/4.0 (compatible; MSIE 5.22; Mac_PowerPC)
Build Identifier: http://ftp.mozilla.org/pub/mozilla/releases/mozilla1.2b/mozilla-macosX-1.2b.smi.bin


On launch, Moz freezes at splash screen..... Proceeds to "creating first window..." 
message, then freezes.

The menu bar is empty.

Moz responds to Quit command in Dock and to Command-Q

Reproducible: Always

Steps to Reproduce:
1. Launch Mozilla
2. Freeze


Actual Results:  
Frozen at  slashscreen with "Creating first window..." message.

Expected Results:  
Splash screen should disappear and browser window should open up.
*** Bug 176122 has been marked as a duplicate of this bug. ***
*** Bug 176120 has been marked as a duplicate of this bug. ***
*** Bug 176119 has been marked as a duplicate of this bug. ***
*** Bug 176121 has been marked as a duplicate of this bug. ***
Whoa! Where did all the dupes come from?!!?
klanda@mac.com, you appear to have filed this bug multiple times.

What build ID are you reporting this bug against?
Greg, I do not know where the multiple subs came from... I assumed it was a glitch. In any 
case, I intended only one report.

Re the build id, I cannot launch it, so I cannot get the ID directely, but the build was dl'ed 
from http://ftp.mozilla.org/pub/mozilla/releases/mozilla1.2b/mozilla-macosX-1.2b.smi.bin

Regards,
Ken
klanda@mac.com, try launching the Mozilla Profile Manager file rather than the
Mozilla application itself. Can you then create another profile and successfully
launch Mozilla?
Greg, launching from Profile Manager and creating a new profile allowed my to start up 
Mozilla successfully. However, there was severe mis-alignment of the toolbar GUI (see 
the second image at http://homepage.mac.com/klanda/PhotoAlbum6.html ).

Also, fyi bug http://bugzilla.mozilla.org/show_bug.cgi?id=167663 is alive and well, and 
struck just after I managed to get a Moz browser open via the Profile Manager.

K

I was able to replicate this.  I was running 1.2a, downgraded to 1.1, and
re-upgraded to 1.2a, and I experienced the smae problem.

I went ahead and backed up my profile, and tinkered, and I ended up deleting
chrome.rdf, and wala, mozilla launched.

I can check the file for any sensitive info and send it alonf if anyone wants to
look at it.
This was probably the theme incompatibility bug. You had a theme other than
Classic or Modern selected prior to 1.2b installation and launch, didn't you?
I'd like to confirm this.  Have no idea why it started to happen.  MacOS X 1.2b.  Not using 
a nightly build or anything...  all I did was change the icon!!
(Bug referred to in comment 11 is bug 162891.)
One more report of the same problem:

http://groups.google.com/groups?as_usubject=Creating%20first%20window%20crash

Again a nonstandard theme was being used. Deleting the XUL Fastload File didn't
help, so this would seem different from bug 167523.
Status: UNCONFIRMED → NEW
Component: Browser-General → Themes
Ever confirmed: true
Another "me too" - I originally had 1.1 with an old version of Orbit theme - I
think when I installed 1.2b, it knocked me back to an old theme because it
successfully noticed that that old Orbit theme would not work with 1.2b, so I
upgraded my Orbit theme to the one that said it would work with 1.2b.  I then
upgraded to 1.2, and got the "Creating First Window" hang.  I deleted
chrome.rdf, it started up fine, but all the toolbar images were misaligned.  I
went and picked "Modern" and it works fine now.  Haven't tried reinstalling Orbit.
I have/had the same problem with 1.2 on MacOS 9. Creating a new profile fixes it, though 
it's kind of an annoying work around. I, too, had some third-party theme installed when I 
upgraded.

*** This bug has been marked as a duplicate of 144027 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
*** This bug has been marked as a duplicate of 144027 ***

*** This bug has been marked as a duplicate of 144027 ***
Component: Themes → Skinability
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.