Closed Bug 450504 Opened 13 years ago Closed 11 years ago

[Win32] SeaMonkey 1.1.x Installer should remove SM 2.0 files during downgrade to avoid crash on start

Categories

(SeaMonkey :: Installer, defect)

SeaMonkey 1.1 Branch
x86
Windows 2000
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: sgautherie, Unassigned)

References

Details

(Keywords: crash, qawanted)

If you're going to do this don't leave it for the last minute. I don't think the crash was confirmed though, just suspected.
Flags: blocking-seamonkey2?
Keywords: qawanted
This should possibly block 1.1.x release not 2.0.x release.
Flags: blocking-seamonkey2?
Flags: blocking-seamonkey2-
Flags: blocking-seamonkey1.1.19?
Severity: normal → critical
Keywords: crash
(In reply to comment #1)
> If you're going to do this don't leave it for the last minute. I don't think
> the crash was confirmed though, just suspected.

You're correct, Daniel.  I am unable to make the SM 1.1.18 "crash" after installing it on top of SM 2.0 and overwriting the SM 2.0 files on my WinXP computer with the SM 1.1.18 files.  Don't know why Serge has to file a bug report about this in the first place when in fact the "crash" does not seem to occur at all.  I'll try to install SM 1.1.18 on top of SM 2.0 on my relative's Win2000 machine and check there if things go either good or bad.
(In reply to comment #3)
> Don't know why Serge has to file a bug report about this in the first place

'Unconfirmed' means "check to be sure we're not missing something"...
fair enough Serge.  any chance of you developing a patch for this suspected bug?
bug 450364 for TB hasn't been fixed yet either.
Nobody did pick this up, so 1.1.19 doesn't have it and it marks the end of the line for SeaMonkey 1.x so this is WONTFIX.
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Flags: blocking-seamonkey1.1.19? → blocking-seamonkey1.1.19-
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.