Closed
Bug 243860
Opened 20 years ago
Closed 20 years ago
Profile migration completely busted if only a "phoenix" profile exists
Categories
(Firefox :: Migration, defect)
Firefox
Migration
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: MMx, Assigned: bugs)
Details
Attachments
(2 files)
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040514 Firefox/0.8.0+ (MMx2000) Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040514 Firefox/0.8.0+ (MMx2000) If there exists only a "phoenix" (->Fx0.8) profile for a user, the first-run Migration Manager does not work. If e.g. a "mozilla" profile exists, everything works fine. (Phoenix profile gets migrated) Reproducible: Always Steps to Reproduce: 1. use a fresh user (no browser profiles) 2. launch Fx0.8, let it create profile, close 3. launch recent nighty Actual Results: an unusable Migration Manager window appears, "Next" does not work, no selection possible in checkboxes Only "esc" helps to get rid of it (OS X) profile is *not* converted. A fresh profile is created. Expected Results: migrate the "phoenix" profile without any hassle Bug 238056 might be related to that selecting "platform: all" and "OS: all" because of bug mentioned above.
Reporter | ||
Updated•20 years ago
|
Flags: blocking1.0?
Reporter | ||
Comment 1•20 years ago
|
||
This is how the migration manager looks like if *only* the "phoenix" profile is present
Reporter | ||
Comment 2•20 years ago
|
||
This is how it looks if also a Mozilla profile is present
I can't reproduce this (logging on as user who has never used this PC before): Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7) Gecko/20040601 Firefox/0.8.0+
Comment 5•20 years ago
|
||
Still an issue?
Comment 6•20 years ago
|
||
no updates in a month, I'm pretty sure we fixed these dialogs already. minusing and resolving WFM
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Flags: blocking-aviary1.0? → blocking-aviary1.0-
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•