113593 - uninstall doesn't remove all files

Status: RESOLVED WORKSFORME

(SeaMonkey :: Installer, defect)

Description

[Henrik Gemal]

after the "inspector" where added to the install, this file:
c:\Program 
Files\mozilla.org\Mozilla\chrome\overlayinfo\inspector\content\overlays.rdf
doesn't get deleted when uninstalling mozilla.

uninstall also leaves this file:
c:\Program Files\mozilla.org\Mozilla\chrome\chrome.rdf
and this directory:
c:\Program Files\mozilla.org\Mozilla\components\Netscape\
behind.

build 20011203

Comment 1

[Henrik Gemal]

*** Bug 114599 has been marked as a duplicate of this bug. ***

Comment 2

[Syd Logan]

reassigning

Comment 3

[Karl Johan Kleist]

see also Bug 125877 

Comment 4

[Henrik Gemal]

*** Bug 135642 has been marked as a duplicate of this bug. ***

Comment 5

[Andrew Hagen]

Looks like this bug calls for only two more files to be deleted.

Comment 6

[Pete Boyd]

uninstall on Windows also doesn't remove:
%WINDIR%\MozillaUninstall.exe
%WINDIR%\mozver.dat
%WINDIR%\nsreg.dat [bug 142367]

we ask people to remove these by hand when they uninstall - this should not be
the user's responsibility but the mozilla uninstaller's

Comment 7

[Daniel Veditz [:dveditz]]

mozver.dat is shared between multiple mozilla instances

nsreg.dat is a mistake in the first place.

The uninstaller should probably remove itself after it's done successfully. It
can also be shared between multiple mozilla instances so it'd need to check the
registry first to see if other Mozillas are registered.

Comment 8

[Henrik Gemal]

we also miss "compreg.dat"

Comment 9

[Jason Bassford]

If the uninstall routine were properly implemented, we wouldn't have to worry
about bug 162593 or bug 165199.

Comment 10

[Boris 'pi' Piwinger]

Not sure what exactly should be removed. Certainly everything which has
significant information MUST NOT be removed. Is it true, that all those things
are in the user profile directories? Well, no, at least the plugins are not.
Anything else?

pi

Comment 11

[David G King]

I'm upgrading this to Major based on Bug #165199 where it was demonstrated that
this bug prevented Mozilla from being usable (even after uninstalling the
previous version).

Comment 12

[Henrik Gemal]

doing a Mozilla install (20020904) on a clean system leaves these file behind 
when doing a uninstall:

C:\Program 
Files\mozilla.org\Mozilla\chrome\overlayinfo\cookie\content\overlays.rdf
C:\Program 
Files\mozilla.org\Mozilla\chrome\overlayinfo\inspector\content\overlays.rdf
C:\Program Files\mozilla.org\Mozilla\components\compreg.dat
C:\Program 
Files\mozilla.org\Mozilla\components\Netscape\MozillaTrunk\manifest.ini
C:\Program 
Files\mozilla.org\Mozilla\components\Netscape\MozillaTrunk\permdata.box
C:\WINNT\MozillaUninstall.exe
C:\WINNT\mozver.dat

And we still leave a whole stuff in the reg.db behind. Please see bug 125877 
for that...

Comment 13

[Eva Vanamee]

This seems like a serious problem because it is impossible to have a clean
install afterwards. The old problems are moved onto the new installation. 

Comment 14

[José Jeria]

This blocks bug 171441 too.

Comment 15

[David G King]

I'm not sure if technically, this blocks Bug #171441, or that bug is a dup of
this one. For now, I'm going to mark it as being blocked by this one.

Comment 16

[Torben]

*** Bug 135017 has been marked as a duplicate of this bug. ***

Comment 17

[David G King]

I'm removing the block on Bug #171441 that I added earlier. Two reasons, that
bug has been fixed, and it also (sort of) deals with the COMPREG.DAT file
mentioned in Comment #12 (by deleting it on install). Mind you, if it deletes it
on install, then it's perfectly valid to delete it on uninstall as well.

Comment 18

[Flaky Jake]

Also talkback is left behind when uninstalling. I think uninstaller should ask
you if you like your profile deleted or not. Also if to delete the install dir
which likely contains plugins + etc stuff not installed by original Firefox
install. Non-functional uninstallers are very annoying.

Comment 19

[Matthias Versen [:Matti]]

Seamonkey and Firefox are using a new NSIS based installer. resolving this old bug, please reopen if you still get this with the new installer