After installation and running N6 for the first time with 4.x profile the profile migration completes. But on the second startup it runs through profile migration again. Steps to reproduce: 1) Install N6 HPUX Beta1 version (20010214) 2) Make sure you have a 4.x profile (.netscape) 3) Startup N6 4) Check that profile migrates into N6 5) Exit N6 6) Restart N6 Result: It goes through profile migration again. This problem only happens starting N6 for the very first time. Then on profile migration will only occurs once if no .mozilla profile exist. This problem was also found on Linux with the 6.01RTM build. But the latest night build does not have this problem. It also generates an error at the very first run: ************************************************************ * Call to xpconnect wrapped JSObject produced this error: * [Exception... "Factory not registered (may be tried again) [nsIModule::registerSelf]" nsresult: "0x80040155 (NS_ERROR_FACTORY_REGISTER_AGAIN)" location: "<unknown>" data: no] ************************************************************

change QA to myself

To clarify: - this only happens the 1st and 2nd times a set of bits are run - to reproduce I would need to un-zip and un-tar a tarball

Saw this on Linux 6.1 2/19 installation also

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

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

nominating for nsbeta1 and mozilla 0.9. after running ./mozilla -installer, my 4.x profile is created, but in the ~/.mozilla/ dir the registry file is missing. i quit the app and restart [via ./mozilla -P sairuh], and get the Create Profile dialog. i give the same name as my migrated profile. after this the ~/.mozilla/registry is created, and subsequent attempts to launch via ./mozilla -P sairuh work fine.

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

deletion of the components.reg and the .mozilla file will reproduce the problem on the subsequent 2 runs. However merely deleting the components.reg does not cause the migration again. There seem to be some weird things happening in profile migration. I'll be digging through this process for the next couple days.

at first run through some of the code, I noticed in nsProfileAccess::UpdateRegistry() that it appears quite possible to not have enough information to actually have a registry, although I haven't traced through a run to see what the actual situation is. this may cause the situation sairuh saw.

nominating for nsdogfood, as this could really confuse users.

This is identical to bug 71527

As bzbarsky pointed out, it is a dup of bug 71527 - marking it as such since there is already a patch on that bug with r= and just awaiting sr=. *** This bug has been marked as a duplicate of 71527 ***

Verified dup.