Updating to Firefox 67 switches to a new Profile, makes users worry about old profile

onebuck · 05-30-2019, 11:56 AM

Hi,

Just a heads up for those that choose to update Firefox 66 to 67 and think you lost profiles;

Quote:

Updating to Firefox 67 switches to a new Profile, makes users worry about old profile

Last Updated: May 25, 2019By Venkat in Firefox, News 4 Comments Tags: mozilla

If you’ve upgraded from Firefox 66 to 67 and noticed your bookmarks, add-ons no longer there in Firefox, you’re not alone! This issue is bothering a lot of users right now where Firefox creates a new profile and makes it as default, don’t fret! Your old profile is still there here is how you can switch to it easily, meanwhile, Mozilla is still collecting information on what went wrong with new profile per install architecture feature they introduced with Firefox 67.
Users who have updated Firefox 66.0.5 to Firefox 67 complaining the new Firefox update wiped old profile data or done a reset to customization, which is not the case, Firefox created a new profile and made it as default, in this case, this could’ve happened if you’ve run beta or Nightly version of Firefox before. This has been done to prevent release profile from mixing with beta or nightly versions which can cause data ls and some other issues.

I experienced this when I updated my Slackware64 Firefox browser package. After some investigation I found the above article to be helpful. For Slackware Firefox package updates I use ruario's script; https://gist.github.com/ruario/9672798

Hope this helps.
Have fun & enjoy!

scasey · 05-30-2019, 04:06 PM

Thanks for the heads-up, onebuck.

Interestingly, I did NOT have the described problem upgrading Firefox from 66 to 67 on either this CentOS/Cinnamon desktop or my Windows10 box.