Issues running Dedicated profile with Profile Manager
Categories
(Toolkit :: Startup and Profile System, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox64 | --- | unaffected |
| firefox65 | --- | unaffected |
| firefox66 | --- | unaffected |
People
(Reporter: Ovidiu, Assigned: mossop)
References
Details
(Whiteboard: qablocker )
[Affected platforms]:
Tested on Mac OS X 10.14 and Windows 10
[Steps to reproduce]:
Prerequisites: Set up the browser to open Profile Manager
- Open a build that has a dedicated profile set up
- Close the browser
- Open again the build from step 1
[Actual result]:
The browser does not open.
[Expected result]:
The browser should open.
Note:
If the Profile Manager is not activated the issue is not reproducible. Here is a video with the issue: https://streamable.com/mvlsq
|
Reporter | |
Updated•5 years ago
|
|
Assignee | |
Updated•5 years ago
|
|
|
Assignee | |
Comment 1•5 years ago
|
||
Ok, figured this out. Will do some builds later today that fix this.
|
|
Reporter | |
Comment 2•5 years ago
|
||
First time when you open the browser after you've installed it the Profile Manager is not prompted. If I restart the browser the Profile Manager is shown, I want to know if this is the expected behaviour, or we should see the Profile Manager at first start of the browser?
|
|
Assignee | |
Comment 3•5 years ago
|
||
(In reply to ovidiu boca[:Ovidiu] from comment #2)
First time when you open the browser after you've installed it the Profile Manager is not prompted. If I restart the browser the Profile Manager is shown, I want to know if this is the expected behaviour, or we should see the Profile Manager at first start of the browser?
This is kind of a carry over from previous behaviour. If Firefox had never been run (there are no profiles) but (somehow?) has a profiles.ini that says to always show the profile manager it would just create a new profile and mark it as default.
So the new code, if it thinks it is the first run of an install (determined by seeing if it has ever had a default profile assigned to it) we ignore that setting and just create a new default profile.
I lean towards this being correct, showing the profile manager would tempt users to just select a profile that is for a different install, but let's hear what Romain and Michael think.
|
||
Comment 4•5 years ago
|
||
On first run after the update users would get a new profile created and have a chance to be educated about the new behavior - they can still close the browser and re-open it to see the profile manager.
If I get this right, I agree that the current behavior on first run seems correct since otherwise profile manager + information UI would be very confusing.
My recollection of what we want when the profile manager is set to open automatically:
1 If browser install is eligible for a new default profile, set new default profile and inform the user per agreed UI
2 Close the browser
3 Open the browser, see the profile manager
|
||
Comment 5•5 years ago
|
||
(In reply to Dave Townsend [:mossop] (he/him) from comment #3)
So the new code, if it thinks it is the first run of an install (determined by seeing if it has ever had a default profile assigned to it) we ignore that setting and just create a new default profile.
I lean towards this being correct, showing the profile manager would tempt users to just select a profile that is for a different install, but let's hear what Romain and Michael think.
Yes, I agree.
Description
•