219839 - XPInstall uninstall fails when package registry name contains multiple level of path

Status: RESOLVED EXPIRED

(Core :: XPCOM, defect)

Description

[Wang Xianzhu]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624

In modules/libreg/src/VerReg.c, VR_UninstallCreateNode function put uninstall
information into version registry, without converting regPackageName and leave
'/'s in it.  However, VR_GetUninstallUserName fetches information from version
registry after converting regPackageName by change '/'s into '_', which results
'component not found' error.




Reproducible: Always

Steps to Reproduce:
1. Create an install package testinst.xpi, containing the following install.js
scripts:
   initInstall('testinst', '/Runway/Racer/testinst', '0.2');
   add...
   add...
   ...
   performInstall()
This will succeed.  Information in install.log and mozver.dat are all correct.
2. Create another install package testunins.xpi, containing the following
scripts to uninstall testinst:
   initInstall('testinst', '/Runway/Racer/testinst', '0.2')
   uninstall('Runway/Racer/testinst');
   ...
   performInstall();


Actual Results:  
Mozilla reports -213 error when uninstall performed.



Uninstall information in mozver.dat(Using a modified version of regExport):
PRIVATE/Mozilla/XPInstall/Uninstall/Shared/Runway
PRIVATE/Mozilla/XPInstall/Uninstall/Shared/Runway/Racer
PRIVATE/Mozilla/XPInstall/Uninstall/Shared/Runway/Racer/testinst
        PackageName = String [testinst]

VR_GetUninstallUserName tries to find /Runway_Racer_testinst key in the version
registry, which does not exist.

Comment 1

[Wang Xianzhu]

A correction: 

in Steps to Reproduce 2:
   uninstall('Runway/Racer/testinst');
should be
   uninstall('/Runway/Racer/testinst');
(This is only a mistyping when submit this bug)

Comment 2

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 3

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.