Closed
Bug 183391
Opened 22 years ago
Closed 22 years ago
Mozilla 1.2.1 hangs after install from 1.0.1 or 1.2
Categories
(Core Graveyard :: Skinability, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 144027
People
(Reporter: shad, Assigned: asa)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.1) Gecko/20020826
Build Identifier: http://ftp.mozilla.org/pub/mozilla/releases/mozilla1.2.1/mozilla-win32-1.2.1-installer.exe
After installing Mozilla 1.2.1 the browser and quick launch function hangs while
launching. The Mozilla splash will load and stay on the screen.
I have reproduced this when installing from 1.0.1 and from 1.2. When
uninstalling and reverting back to 1.0.1 the browser and quick launch work fine.
Reproducible: Always
Steps to Reproduce:
1. Start with 1.0.1 or 1.2
2. Install 1.2.1
3. Attempt to launch Mozilla
Actual Results:
Splash displays and Mozilla hangs. When checking the task manager everything
looks normal. Mozilla is using nominal amounts of memory and processor cycles
are at zero.
Expected Results:
Browser should launch and load.
Windows XP SP1
AMD Athlon 2100+
ASUS A7v 333
Geforce 4 MX 440 64MB
WD 80gb HDD
256MB 333MHz DDR
Norton AV 2003 running in memory
Comment 1•22 years ago
|
||
Reporter : you *have* to uninstall any previous version of Mozilla before
installing a new one.
http://www.mozilla.org/releases/mozilla1.2.1/
"Installation Notes
Install into a new empty directory. Installing on top of previously installed
builds may cause problems."
Resolving this bug as invalid ?
Reporter | ||
Comment 2•22 years ago
|
||
The first time I installed I just installed over the top. The second time I did
an uninstall and even removed the profile from the application data folder.
Whether I performed an over the top install or a clean install after
uninstalling the problem occured. Forgot to mention that... sorry.
As a matter of usability the solution should not be: You need to install Mozilla
to a clean directory when upgrading to the new version. The unistall routine
should be written to remove ALL remnants of the previous version and then do the
upgrade to the new version, especially if you are just suggesting they install
to a new directory anyway... save them the trouble. Even then when possible it
would make sense to allow an upgrade over the exisitng software and such so
settings stay intact.
Comment 3•22 years ago
|
||
does deleting registry.dat help?
Reporter | ||
Comment 4•22 years ago
|
||
Under WindowsXP registry.dat does not exist.
> Under WindowsXP registry.dat does not exist.
It may be hidden, set up your win to show all files and folders.
Your problem are probably caused by incompatible themes in your profile, try to
create a new profile or delete chrome.rdf from the old one.
*** This bug has been marked as a duplicate of 144027 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Component: Browser-General → Skinability
Resolution: --- → DUPLICATE
Updated•17 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•