Closed
Bug 9783
Opened 25 years ago
Closed 25 years ago
[PP]Profile Manager does not present CreateProfileWizard when no 4.x or 5.0 profiles exist
Categories
(Core Graveyard :: Profile: BackEnd, defect, P3)
Tracking
(Not tracked)
VERIFIED
FIXED
M9
People
(Reporter: agracebush, Assigned: racham)
Details
Not sure this is a 'real' bug, but it does not behave quite like 4.x so wanted
to record. With no profiles on the system, I expect to see Create Profile
Wizard first.
Steps to Reproduce:
1)Remove any 4.x profiles/5.0 profiles and mozregistry.dat
2)Launch apprunner (with apprunner -ProfileManager or apprunner -installer)
Actual Results: Profile Migrator window comes up showing no profiles to migrate
or to select - with option to create new
Expected Results: Create Profile Wizard (as in 4.x)
Build Date & Platform Bug Found: 1999071310
Additional Builds and Platforms Tested On: Win only since Linux and Mac do not
have this feature yet
Updated•25 years ago
|
Assignee: selmer → racham
Comment 1•25 years ago
|
||
Bhuvan, this looks like one for you to investigate. If it's real, please set
the TFV as appropriate. Thanks, Steve
Updated•25 years ago
|
Target Milestone: M9
Comment 2•25 years ago
|
||
Setting TFV=M9, we need to look at this pretty soon.
That's right....
The app should go to Profile Wizard, not Profile manager, if the number of
profiles is ZERO. This will be fixed in M9.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
I added the logic to take care of different cases when the apprunner is ran with
-installer flag.
Here are the scenarios when ran with -installer option:
Number of 4x Profiles : Number of 5.0 Profiles : Result
0 0 CreateProfileWizard
0 1 AppRunner
>= 1 >=0 ProfileManager
Reporter | ||
Updated•25 years ago
|
Status: RESOLVED → VERIFIED
Reporter | ||
Comment 5•25 years ago
|
||
build 1999072808
Moving all Profile Manager bugs to new Profile Manager Backend component.
Profile Manager component to be deleted.
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
•