[Dedicated Profiles] User loses access to default profile when setting the MOZ_LEGACY_PROFILES
Categories
(Toolkit :: Startup and Profile System, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr68 | --- | wontfix |
People
(Reporter: cbaica, Unassigned)
References
Details
[Affected versions]:
- Fx68.0 ESR
[Affected platforms]:
- macOS 10.14
- Ubuntu 18.04
- Windows 10 x64
[Steps to reproduce]:
- Have the latest release and latest esr builds available(ESR 68 can be downloaded from this link).
- Set the environment variable MOZ_LEGACY_PROFILES=1.
- Launch ESR 68 then close it.
- Launch the latest release, close it and try to relaunch ESR 68.
[Expected result]:
- ESR should still work with the default profile.
[Actual result]:
- The downgrade protection kicks in.
[Regression range]:
- This is not a regression.
[Additional notes]:
- Please note that most of the users will not use the MOZ_ALLOW_DOWNGRADE along with the legacy profiles variable since there is no instructions that that is needed for a smooth transition to the old behavior of having one profile for everything
- Any version used besides ESR will have a newer version number than ESR so the downgrade protection will always be displayed for the users that have beta/release/nightly installs paired with ESR.
Comment 1•5 years ago
|
||
I'm not sure I'm seeing the issue here, isn't this just downgrade protection working as intended?
Comment 2•5 years ago
|
||
Why is downgrade protection kicking in when ESR and non ESR have the same version?
Reporter | ||
Comment 3•5 years ago
|
||
@Dave: Yes, that's how the downgrade protection works, but then it makes no sense to have ONLY the dedicated feature turned off for ESR- if it only raises more problems for users that have multiple installs. This just means that the user data will not end up on the ESR build, but on the latest nightly/beta/release installed on that machine.
T0: esr60
ESR60 uses default
Release 68 uses default (default dedicated)
T1: esr 68
MOZ_LEGACY_PROFILES 1
MOZ_ALLOW_DOWNGRADE 0
first start: ESR68 uses default
first start: Release 68 uses default
second start: ESR68 - downgrade protection --> user is forced on new profile
@Mike: The downgrade protection looks at more than just the version number. It also compares build ID's to see which one was published earlier/later. I'm not aware of all the technical stuff, but Dave will most likely know it.
Comment 4•5 years ago
|
||
(In reply to Cristian Baica [:cbaica], Release Desktop QA from comment #3)
@Dave: Yes, that's how the downgrade protection works, but then it makes no sense to have ONLY the dedicated feature turned off for ESR
Dedicated profiles are not currently turned off for ESR. We've given administrators the ability to turn it off if they wish and they also have the ability to turn off the downgrade protection if they wish.
Comment 5•5 years ago
|
||
This appears to be working as expected. If folks want both downgrade protection off and legacy profile selection then they can just set two environment variables rather than one.
Updated•5 years ago
|
Description
•