Closed
Bug 185721
Opened 22 years ago
Closed 22 years ago
Upon upgrade from 1.2.0 to 1.2.1 browser and mail/news components cannot both be launched (externally or via internal menu/quick launch features)
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 144027
People
(Reporter: edds, Assigned: asa)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2) Gecko/20021126
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2) Gecko/20021126
Launch browser. Takes 10 seconds. Then, attempt to open mail/news fails
(either via menu or quick launch). Exit browser. Launch mail/news. Takes 10
seconds. Then, attempt to open browser fails (either via menu or quick launch).
Exit mail/news. Lauch browser. Takes 10 seconds. Browser and mail/news
cannot be both lauched. Problem surfaced after attempted upgrade from 1.2.0 to
1.2.1. Problem not fixed with 1.3 uprade or 1.2.0 downgrade. Problem persists
after reboot. URLs in e-mails attempt to load browser but fail (no
notification, program just fails to load).
Reproducible: Always
Steps to Reproduce:
1. Lauch browser
2. Attempt to lauch mail/news
3. Must quick browser, then launch mail/news
4. Problem works in reverse, too (1. Lauch mail/news ...)
Actual Results:
Cannot have both portions of application suite lauched at same time.
Expected Results:
I'd like to have my mail/news open and also be able to browse the Internet.
Nothing unusual. Problem surfaced only after upgrade from 1.2.0 to 1.2.1, and
will not go away with attempts to up/downgrade application.
Updated•22 years ago
|
Summary: Upon upgrade from 1.2.0 to 1.2.1 browser and mail/news components cannot both be lauched (externally or via internal menu/quick lauch features) → Upon upgrade from 1.2.0 to 1.2.1 browser and mail/news components cannot both be launched (externally or via internal menu/quick launch features)
Comment 1•22 years ago
|
||
Reporter:
Close mozilla including quicklaunch, locate your mozilla user profile in your OS
user directory (see the release notes for the path) and delete all files in:
profile\chrome\*.*
YOu will loose all additional installed Themes
Comment 2•22 years ago
|
||
got mail, it works now.
This is a bug and you can only avoid it if you don't install additional
third-party Themes :-)
currently : no new windows -> delete Chrome\*.* , freeze if opening mail or the
preferences -> delete xul.mfl :-)
*** This bug has been marked as a duplicate of 144027 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•