Closed
Bug 282001
Opened 20 years ago
Closed 20 years ago
Only one browser window may ever be opened
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: ddkilzer, Unassigned)
Details
Tonight I upgraded Mozilla on my Win XP SP1 PC from version 1.7.2 to 1.7.5. I did NOT uninstall 1.7.2 first, but instead ran the installer for 1.7.5 and let it clean up the previous installation. Note that I did have a version of LiveHttpHeaders installed with 1.7.2. After installing, the new version of Mozilla 1.7.5 started up just fine. However, I couldn't open a second browser window (or the Profile Manager) while the first browser window was open. Double-clicking on a short-cut, Ctrl-N and selecting File->New->Navigator Window don't have any effect. I tried uninstalling 1.7.5, rebooting, then reinstalling 1.7.5, but this didn't work. I had the same issues as above. After playing some more with 1.7.5, I noticed that SOMETIMES, when the "X" box in the upper right-hand corner of the Window is used to close the single browser window, the "mozilla.exe" process won't exit (by looking at the Task Manager's process list). Killing this process is the only way to reopen a new browser window again. If old process isn't killed, double-clicking on the "Mozilla" icon does nothing. (The cursor changes to the hourglass cursor, but then changes back as soon as the mouse is moved.) The "mozilla.exe" process has ALWAYS exited when File-Exit is used. I even tried uninstalling 1.7.5, rebooting, and reinstalling 1.7.5 a third time, but the behavior persists. Note that I also have Firefox 1.0 installed on this PC. It doesn't matter whether I install with "Quick Launch" enabled or not.
| Reporter | ||
Comment 1•20 years ago
|
||
Well, I feel silly now. After re-installing a new version of LiveHttpHeaders (0.10), Mozilla is working properly again. So if anyone wants to reproduce this issue (roughly speaking): 1. Install Mozilla 1.7.2. 2. Install LiveHttpHeaders 0.9. 3. Install Mozilla 1.7.5. Pain.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
| Reporter | ||
Updated•20 years ago
|
Status: RESOLVED → VERIFIED
Updated•20 years ago
|
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
Comment 2•20 years ago
|
||
This was not a Mozilla bug, so it could not be "fixed".
Status: REOPENED → RESOLVED
Closed: 20 years ago → 20 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•