STR: 1) Create a new profile 2) Launch that profile when it is the default (ie. use profile manager) 3) Click the button to reset your profile from about:support Expected result: Migration UI is shown on startup and data from the profile in #1 is copied to the new profile. Actual result: "Invalid migrator key specified or source does not exist." in error console Also, when working around that problem, you will hit "startMigration was asked to open auto-migrate from a non-existent source Firefox" since gProfileStartup is not set early enough to use in sourceExists. Call stack (hand-made): * migrate ** getMigrator *** sourceExists **** MigrationUtils.isStartupMigration but gProfileStartup is only set in MU_showMigrationWizard which is called after getMigrator is called on startup. Requesting tracking since this breaks the profile reset feature.
5 years ago
Mano, we really need this fixed on Aurora and Nightly because the feature is getting publicity and SUMO articles are written for it: https://support.mozilla.org/en-US/kb/reset-firefox-easily-fix-most-problems
D: Yeah, we need to get this fixes asap, since we're already _well_ into this release cycle.
The patch in bug 748569 fixes this.
I'll try to do that review today
5 years ago
Fixed by bug 748569.
[Triage Comment] Updating status flag to 'fixed' as per comment 7
qa+'ing for verification and removing qawanted
Verified as fixed on: Mozilla/5.0 (Windows NT 6.1; rv:14.0) Gecko/20100101 Firefox/14.0 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:14.0) Gecko/20100101 Firefox/14.0 Mozilla/5.0 (X11; Linux i686; rv:14.0) Gecko/20100101 Firefox/14.0 BuildID: 20120612164001 Also verified on the 2012-06-11 Aurora and Nightly builds on Windows 7, Mac 10.7 and Ubuntu 11.10 32-bit.