Closed Bug 183717 Opened 23 years ago Closed 23 years ago

Mozilla startup fails after bringing up banner window

Categories

(SeaMonkey :: General, defect)

x86
Windows ME
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: cpj1, Assigned: asa)

Details

User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows 98; Win 9x 4.90) Build Identifier: http://www.mozilla.org/releases/ Mozilla 1.2.1 refuses to start up, or maybe refuses to bring up a starting window. A reboot and then a fresh install didn't correct the problem. The Mozilla logo comes up, and then the program hangs. Task Manager still lists a Mozilla application running, so I can shut it down from there. A second attempt to run it (before a reboot) will do nothing. On last successful use, Mozilla was unable to open new windows, but was able to open new tabs. The last website visited was Orbitz.com. Reproducible: Always Steps to Reproduce: 1. Double-Click Mozilla icon 2. 3. Actual Results: Mozilla mascot logo comes up. Startup halts at this point. Expected Results: A new mozilla window should appear when startup is successful.
Reporter : Please run "mozilla -profilemanager" and create an additional test profile
Chris, do you use third party themes? If yes, then they might be the cause (incompatible after update). In addition to creating a new test profile please try removing the 'chrome' folder from your profile directory. This *might* help you keep the old profile and solve both of your problems (see bug 144027).
That did it. After I installed 1.2, I grabbed a compatable copy of the Orbit theme. Then I upgraded to 1.2.1. Initially, Mozilla started out with no theme, so I assumed that it had a problem with Orbit and just reverted back to the default. Thanks.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
.
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago23 years ago
Resolution: --- → WORKSFORME
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.