Closed Bug 184554 Opened 22 years ago Closed 22 years ago

windows not opening

Categories

(SeaMonkey :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: aries_wanderer, Assigned: asa)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130 I apologize. I am certain this is already covered somewhere, but I was not able to find it in the bugfiles (because there were too many hits). I was using Mozilla on my other PC and it functioned correctly. I have a new PC, downloaded Mozilla, and now, when I attempt to open a new window, it immediately disappears and I have only the initial window. This happens if I use ctrl-n, or right click on a link (my preferred method) and select "Open link ...", or when I click on a link set to open to a new browser window AND even when I click on Help-About Mozilla in Mozilla, the window appears and immediately disappears. Do I have a bad copy of Mozilla (1.2.1 I think) or what am I doing wrong? Reproducible: Always Steps to Reproduce: 1. Read the details please. 2. 3. Actual Results: Windows disappear. Expected Results: Stayed open with multiple browser windows.
Try this: close mozilla, then delete all files in the Profile subfolder Chrome/*.* If that does not help: quit again, then delete XUL.mfl in the profile directory. Please report back and tell how it went. Also: Was this the VERY first time any Mozilla-related build was installed on the PC? (Has Netscape6 been installed there earlyer?) Possible duplicate of bug 144027
David, are you still seeing this after deleting the mfl file? Is it the first time Mozilla/Netscape was installed?
Please reopen this bug report if deleting the mfl file did not fix the problem.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
*** Bug 231114 has been marked as a duplicate of this bug. ***
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.