Closed
Bug 49823
Opened 25 years ago
Closed 25 years ago
netscape6 does not recognize and import nova profiles correctly
Categories
(Core Graveyard :: Profile: Migration, defect, P3)
Tracking
(Not tracked)
VERIFIED
INVALID
People
(Reporter: nitinp, Assigned: racham)
Details
I found this strange behavior.
1) I installed a build of netscape6 few days ago and imported my nova
profile(nitinp) into users50.
2)Then recently I removed all the profiles , netscape6 directory, mozregistry ,
mozver , netscape6 from the regedit and installed a new build of netscape6. When
I chose nitinp as the profile it did not bring up the dialog for importing the
files from nova profile.
3) Moreover it did not import anything because db was unintialized.
4) Then I went back and chose a another nova profile to be used in netscape6 and
it brought up the dialog to import the nova profile.
5) )I installed a new build today and now both nitinp and the other profile does
not import even after I removed all the necessary files.
6) The third nova profile does bring up the import dialog.
This is not good at all. We have to fix this.
This is a profile migration proglem.
Assignee: ssu → dbragg
Component: Installer → Profile Migration
QA Contact: gemal → gbush
Summary: netscape6 does not recognize and import nova profiles correctly → netscape6 does not recognize and import nova profiles correctly
Actually this isn't a migration problem. The migration code is called by
Profile Manager and it looks like the Profile Manager might not be reading the
appropriate files to determine if the migration code should be called.
Reassigning to Profile Manager folks.
Assignee: dbragg → racham
Comment 3•25 years ago
|
||
File registry.dat in C:\windows\mozilla needs to be removed also-
this is new-- starting 8/16 I think.
yes...try what Grace has suggested..you should be OK I think.
If you don't where your HOME points to search for file registry.dat under folder
Mozilla and delete that one...and then retry the builds...
This is an invalid bug.
Please follow the steps posted in the previous steps. In your case, you are
simply referring the registry.dat file data. If you need to on clean slate,
please remove registry.dat also.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
Updated•9 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•