is default-release profile a bug or the new profile name for Firefox 67 upwards and still being phased in
Since updating to Firefox 67, myself and my clients either have a **.default or a **.default-release profile. This is despite the fact that we only have one version of Firefox installed and some computers have the -release profile whereas others don't for some reason.
I am aware that a number of people have reported this. However, it's not clear if this is a bug where there is only one version of Firefox installed or intended result.
My main question is going forward will Firefox be using the -release format or the .default profile? In other words, was there a bug in a Firefox version causing it to create a -release profile even if there if there was only one Firefox version installed or is it just a case of some computers have not phased in the new profile name yet. This would explain the inconsistencies between computers.
The reason that this is a problem is because I use a script to install ublock origin and also to copy a user.js preferences file to configure Firefox. I am now having to copy to both -release and .default profiles on every computer and I have designed the script to install ublock to a -release profile.
I would prefer to have one profile moving forward, but need to know whether this will be .default-release or simply .default. Thank you
Vahaolana nofidina
Firefox 67 and later can use a dedicated profile for each of the Firefox update channels (release, beta, nightly, developer-edition,esr68) and will lock the profile, so it can only be used by Firefox in a specific installation folder. For Release versions this profile would be a xxxxxxxx.default-release profile, profiles used in older Firefox versions usually used a xxxxxxxx.default profile (a refresh adds a time stamp).
- https://support.mozilla.org/en-US/kb/dedicated-profiles-firefox-installation
- https://blog.nightly.mozilla.org/2019/01/14/moving-to-a-profile-per-install-architecture/
All Replies (4)
Vahaolana Nofidina
Firefox 67 and later can use a dedicated profile for each of the Firefox update channels (release, beta, nightly, developer-edition,esr68) and will lock the profile, so it can only be used by Firefox in a specific installation folder. For Release versions this profile would be a xxxxxxxx.default-release profile, profiles used in older Firefox versions usually used a xxxxxxxx.default profile (a refresh adds a time stamp).
I understand what Firefox 67 is doing with regards to having a dedicated profile for each of the Firefox update channels. That makes sense.
Perhaps a better way to ask the question is why does my computer and laptop have Firefox 67.04 but has xxx.default profiles yet my clients - some computers have xxx.default-release and other computers are like mine with just xxx.default
We are all running Firefox 67.04 and we only have one firefox installed. We don't install different versions. So why are some computers changing the profile to -release whereas other computers upon updating to ver 67 continue to use just xxx.default
Thank you
Previous Firefox versions used a xxxxxxxx.default profile that you can continue to use. Only when a new profile is created then this will be a default-release profile.
cor-el said
Previous Firefox versions used a xxxxxxxx.default profile that you can continue to use. Only when a new profile is created then this will be a default-release profile.
This is what I was expecting to see, but I have noticed that this was not happening. On a couple of computers, I tested this and one created the default-release profile and the other created a default profile. However it may have been because the Firefox versions weren't actually Firefox 67 at the time as I know that Firefox does not update on all computers on the same day necessarily. I also think that there was a bug on I think Firefox 67.01 if I remember rightly.
I will test this again on some computers and see what happens.
thank you.