Closed
Bug 196620
Opened 21 years ago
Closed 21 years ago
WinXP - Nightly builds have crashed since 2003-03-01
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 196725
People
(Reporter: brad.kruse, Assigned: asa)
Details
(Keywords: crash)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030224 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/ The last nightly build that worked for me is Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030224 Since then the installer has crashed just about the time it should launch Mozilla. Attempting to start Mozilla from the Start menu accomplishes the same error crash. Reproducible: Always Steps to Reproduce: 1.Go to www.mozilla.org 2. Download nightly 'Windows' build 3. Execute the downloaded file, accept default options except select 'Quick Launch'. 4. See the Windows pop up 'Report this error to Microsoft?' The TalkBack handler does not come up. Actual Results: Error message WinXP popups, Mozilla does not launch. Expected Results: Mozilla should launch, looking better and being more robust than ever before. (Well, it used to!) I have tried this with at least 10 different downloads since the 1st of March.
Comment 1•21 years ago
|
||
Brad, have you been installing over previous builds, or uninstalling first? Have you tried with a clean profile?
Keywords: crash
I install each download on top of the previous version. This had been working really well for me. I have a lot of emails stashed in folders -- I am not sure what all will change or delete my profile (and email folders), so I haven't been keen to uninstall or start a new profile.
Comment 3•21 years ago
|
||
Uninstalling the old version won't touch your profile. Creating a new profile won't touch your old profile either. When you start Mozilla you can choose which profile to use. The installer is supposed to remove all the stuff from the previous version, but sometimes it leaves something behind.
Comment 4•21 years ago
|
||
Brad, you should never install over a previous build. Always uninstall and delete the old Mozilla directory. http://www.mozilla.org/start/1.0/faq/troubleshooting.html#10.10 Your profile is kept in Documents & Settings, so it won't be affected. Does this solve your problem?
Comment 5•21 years ago
|
||
*** This bug has been marked as a duplicate of 195600 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
If you think that uninstalling previous Mozilla's will solve my problem, then this is *not* a duplicate of 195600. I uninstalled Mozilla 1.3b, I ran Norton SystemsWorks 2002 OneButtonCheckup, I restarted my computer, then installed the nightly build from 3/9/03, 5:46pm CST. I also tried uninstalling Mozilla, went to the Program File\Mozilla.org\Mozilla directories and removed any remaining files before trying to install Mozilla 1.4. The change in symptoms is that now I get the TalkBack popup as well as the windows 'report this error' popup. Mozilla 1.4 is still not installing on my WinXP PC. Mozilla 1.3b still runs without any abnormal symptoms.
Comment 7•21 years ago
|
||
reopening as I see no reason that this bug would be related to bug 195600 have you tried a new profile? there is currently a bug (don't remember the bug number, search for "XBLBinding") related to some of the XUL prefences (cache/directory listing) that can make it consistently crash at startup.
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
Comment 8•21 years ago
|
||
bug 196337, bug 196477 and bug 196446 (which were apparently caused by bug 194834)
Creating a new profile solves the crashing problem. This means that the new Mozilla 1.4 strands my existing profile. This still seems to be a problem, both as an impediment to upgrading, and a drawback that the old profile must be abandoned to make Mozilla work. Could profiles be tagged to indicate the version of Mozilla they are compatible with, so that Mozilla can check the tag and warn the user there is a version conflict? One Talkback error was logged, TB17921138Y. *** This bug has been marked as a duplicate of 196725 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago → 21 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
•