Closed Bug 32509 Opened 25 years ago Closed 25 years ago

4.x profile does not show in Profile Manager to select for migration

Categories

(Core Graveyard :: Profile: BackEnd, defect, P3)

defect

Tracking

(Not tracked)

VERIFIED INVALID

People

(Reporter: agracebush, Assigned: selmer)

Details

Steps to reproduce: 1.Install Linux build 2000-03-20-08-M15 (trunk) 2.Remove ~/.mozilla directory 3. Run ./netscape -profilemanager (or -selectprofile) Actual results: ProfileManager opens with no profiles displayed Expected result: Profile Manager display unmigrated 4.x profile *Note: running ./netscape -installer will automigrate the 4.x profile
On Win trunk build 2000-03-20-09 also netscp6 -ProfileManager not displaying 4.x profiles for migration
Mac trunk build 200-03-20-10 also
OS: Linux → All
Hardware: PC → All
The -installer flag must have been used at least once to make migration happen. If you have not used -installer, then the behavior you're seeing is expected.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
this is first time in a long time I have not seen unmigrated profiles when I use -ProfileManager option- It was more obvious today as I had just finished same tests on beta branch and differences stood out when I installed and tested trunk bit. Don't think this is invalid.
Grace, sorry about the way I worded that. I saw that Seth checked in a fix for the -installer flag over the weekend and assumed you knew that. Anyway, Seth's change puts _back_ the behavior we wanted where profile migration only works when -installer is used and is _not_ done otherwise. Hence, this bug is invalid because the behavior you saw here is actually the one we want.
No problem- I did not hear of the changes
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.