Closed Bug 1553526 Opened 6 years ago Closed 5 years ago

[Profile per channel] Reports of users being switched over to new profiles when upgrading from release 66 to release 67

Categories

(Toolkit :: Startup and Profile System, defect)

Product:
Toolkit
Component:
Startup and Profile System
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INCOMPLETE
Tracking Flags:
Tracking Status
firefox-esr60 --- unaffected
firefox67 --- affected
firefox67.0.1 --- wontfix
firefox68 --- affected
firefox69 --- affected

People

(Reporter: bugzilla, Unassigned, NeedInfo)

References

(Regression)

Details

(Keywords: regression)

(In reply to Aaron Klotz [:aklotz] from comment #0)

https://www.reddit.com/r/firefox/comments/brjj82/firefox_67_thinks_its_an_old_version_and_wont/

This looks like a profile downgrade issue, not a fresh dedicated profile, I've asked them to file a bug.

https://www.reddit.com/r/firefox/comments/broebr/just_updated_to_firefox_67_and_have_a_new_profile/

Asked them to comment here.

https://news.ycombinator.com/item?id=19970335

Looks like this person installs different versions of Firefox to different locations and uses a symlink to select the install. This is probably working as expected.

This happened to me.

My OS is Win10, updated, I updated FF 66 to 67. I also have Nightly with a dedicated profile, as well as a profile called Testing that is self-explanatory.

(In reply to prittman from comment #2)

This happened to me.

My OS is Win10, updated, I updated FF 66 to 67. I also have Nightly with a dedicated profile, as well as a profile called Testing that is self-explanatory.

If this matters, Nightly hadn't been updated since April.

(In reply to prittman from comment #2)

This happened to me.

My OS is Win10, updated, I updated FF 66 to 67. I also have Nightly with a dedicated profile, as well as a profile called Testing that is self-explanatory.

Can you explain a little about how you have nightly using its dedicated profile and how you use the Testing profile?

(In reply to Dave Townsend [:mossop] (he/him) from comment #4)

(In reply to prittman from comment #2)

This happened to me.

My OS is Win10, updated, I updated FF 66 to 67. I also have Nightly with a dedicated profile, as well as a profile called Testing that is self-explanatory.

Can you explain a little about how you have nightly using its dedicated profile and how you use the Testing profile?

Not sure what there is to say. Nightly was my daily driver for a few months, till I realized that release/beta was about as fast--this happened a few months ago, early 2019. Since then, I've only occasionally fired it up. My testing profile only exists if I really want to try out a new profile for troubleshooting purposes. I honestly don't recall when I used FF with it last, probably 6 months ago if not longer.

All my profiles are in their default Win10 Firefox profile directories, if that's what you meant. I don't use FF Sync, everything is on my C partition.

(In reply to prittman from comment #5)

(In reply to Dave Townsend [:mossop] (he/him) from comment #4)

(In reply to prittman from comment #2)

This happened to me.

My OS is Win10, updated, I updated FF 66 to 67. I also have Nightly with a dedicated profile, as well as a profile called Testing that is self-explanatory.

Can you explain a little about how you have nightly using its dedicated profile and how you use the Testing profile?

Not sure what there is to say. Nightly was my daily driver for a few months, till I realized that release/beta was about as fast--this happened a few months ago, early 2019. Since then, I've only occasionally fired it up. My testing profile only exists if I really want to try out a new profile for troubleshooting purposes. I honestly don't recall when I used FF with it last, probably 6 months ago if not longer.

So you had Nightly running and then you switched to release(?). Did that already use a different profile to Nightly and then switched to a new profile again after the upgrade to 67?

Yes to all. I already had nightly running its own profile; then I used the Release and Beta for the last few months, sharing their profile(s). Then, after upgrading to 67, I saw a new profile created and used by 67.

(In reply to prittman from comment #8)

Yes to all. I already had nightly running its own profile; then I used the Release and Beta for the last few months, sharing their profile(s). Then, after upgrading to 67, I saw a new profile created and used by 67.

I'm assuming that nightly was running its own profile because it was already version 67 or higher and not because of any command line arguments in its shortcut.

Ok so sharing the profile between release and beta might have caused this. By any chance did you use Beta immediately before starting Firefox 67 Release for the first time?

I did not modify the shortcut; before today, it was last updated some time (IIRC) 20 April or thereabouts; today I went ahead and updated it to current.

As far as sharing between release and beta, yeah I've jumped back and forth quite a bit between the two using teh same profile. I would just install either over the other (release over beta, beta over release).

I have not used beta (it has not been installed on my machine) in the past 2-3 months--I installed Release over it, or just carried a RC into the release version.

Could you upload a copy of C:\Users\<username>\AppData\Roaming\Mozilla\Firefox\profiles.ini and tell me the installation directories of the versions of Firefox you are using now?

Flags: needinfo?(prittman)

Here is my ini file:

[InstallA3710B8EBB50CD3]
Default=Profiles/ilie146i.Nightly
Locked=1

[Profile2]
Name=Nightly
IsRelative=1
Path=Profiles/ilie146i.Nightly

[InstallCA9422711AE1A81C]
Default=Profiles/eymbiwfk.default
Locked=1

[Profile1]
Name=Testing
IsRelative=1
Path=Profiles/sjtre9cr.Testing

[Profile0]
Name=default
IsRelative=1
Path=Profiles/eymbiwfk.default
Default=1

[General]
StartWithLastProfile=0
Version=2

[Install308046B0AF4A39CB]
Default=Profiles/eymbiwfk.default
Locked=1

[Profile3]
Name=default-release
IsRelative=1
Path=Profiles/hjpfo5n7.default-release

Installation directories:
Release: "C:\Program Files\Mozilla Firefox\firefox.exe"
Nightly: "C:\Program Files\Nightly\firefox.exe"
FDE: "C:\Program Files\Firefox Developer Edition\firefox.exe"

Flags: needinfo?(prittman)

I would like to add that I have experienced this issue as well.

I am using Arch Linux, under the normal release channel (extra/firefox). I updated Firefox before shutting down last night, and when I started it up today it put me in a new profile "default-release". I was able to switch to my old profile without any problems, but saw that input was requested from anyone experiencing the bug so here I am anyway.

Please let me know if you require any more information. For what it's worth, I have not yet removed the new profile.

I have the same issue. Ff 76 generates new profile "default-release", ignoring users standard-profile.
We have Terminalserver environment on Windows Server 2012 R2. Firefox 66.0.5 is virtualized using Microsoft App-V 5.0. Firefox Profile is setup inside home-directory of user, so the correct settings are loaded on any Terminalserver. Previous updates worked perfectly, 58 -> 60 -> 61 -> 65 -> 66.0.5. Now, Ff 67 generates a new profile in C:\xxx... and set's it as default, so all settings are gone. In Profile Manager the old profile is showing and can be selectet. When you run it, it looks good and loads all the settings as it should.
Now I went back to Ff 66, as I don't want the users to go into profile manager to Play with profiles. Ff 67 should do this automatically. I have no workaround for now.

(In reply to Matthew Dimitroff from comment #13)

I would like to add that I have experienced this issue as well.

I am using Arch Linux, under the normal release channel (extra/firefox). I updated Firefox before shutting down last night, and when I started it up today it put me in a new profile "default-release". I was able to switch to my old profile without any problems, but saw that input was requested from anyone experiencing the bug so here I am anyway.

Do you use any other installs of Firefox on your computer?

Can you give me the location of the firefox binary on your computer (following any symlinks).

(In reply to Alex from comment #14)

I have the same issue. Ff 76 generates new profile "default-release", ignoring users standard-profile.
We have Terminalserver environment on Windows Server 2012 R2. Firefox 66.0.5 is virtualized using Microsoft App-V 5.0. Firefox Profile is setup inside home-directory of user, so the correct settings are loaded on any Terminalserver. Previous updates worked perfectly, 58 -> 60 -> 61 -> 65 -> 66.0.5. Now, Ff 67 generates a new profile in C:\xxx... and set's it as default, so all settings are gone. In Profile Manager the old profile is showing and can be selectet. When you run it, it looks good and loads all the settings as it should.
Now I went back to Ff 66, as I don't want the users to go into profile manager to Play with profiles. Ff 67 should do this automatically. I have no workaround for now.

I'm afraid that I don't know much about App-V and the person who does is currently out until Tuesday. Can you explain what it actually does and how it might affect the environment that Firefox thinks it is running in? Particularly what Firefox might think is its installation directory and how you have made the default profile available to it?

Flags: needinfo?(alessandro.luongo)

(In reply to Dave Townsend [:mossop] (he/him) from comment #15)

(In reply to Matthew Dimitroff from comment #13)

I would like to add that I have experienced this issue as well.

I am using Arch Linux, under the normal release channel (extra/firefox). I updated Firefox before shutting down last night, and when I started it up today it put me in a new profile "default-release". I was able to switch to my old profile without any problems, but saw that input was requested from anyone experiencing the bug so here I am anyway.

Do you use any other installs of Firefox on your computer?

Can you give me the location of the firefox binary on your computer (following any symlinks).

At one point (during the app signing issue) I briefly used Firefox Nightly, but it has long since been uninstalled and its profile deleted. I use just the regular version now.

The firefox binary is located in /usr/bin/firefox.

¡Hola Dave!

Ended up while researching on the following questions in the Spanish SuMo forums:

https://support.mozilla.org/questions/1259984
https://support.mozilla.org/questions/1260173
https://support.mozilla.org/questions/1260071
https://support.mozilla.org/questions/1260211
https://support.mozilla.org/questions/1260038

FWIW I've requested them all for copies of their ''installs.ini'' and ''profiles.ini'' files.

Should this one warrant a dot release perhaps or could it be fixed "automagically"?

¡Gracias!
Alex

Hi,

I just encountered the same issue on Win 10 64bit.

I have simply clicked on "restart Firefox to finish the upgrade" and my FF release 66 restarted as FF67 with a blank profile named default-release.
I have also FF dev edition installed.

After reading https://www.ghacks.net/2019/05/27/how-to-fix-firefox-starting-with-a-blank-user-profile/ I tried setting the original profile 42f4yg73.default as default profile from about:profiles and restarted FF but this didn't work, the default-release profile was still used. I then clicked on "Launch profile in a new browser" for 42f4yg73.default and it worked and I closed the previous window (the one on the newly created default-release profile). From the browser window with my old profile launched in the previous step, I went to about:profiles, and deleted the new profile default-release entirely (when the dialog asked to also delete the folder, I said yes). Then I closed that browser window and tried to reopen firefox from the shortcut in the taskbar, but windows said it couldn't find that item. Somehow the binary from the old shortcut cannot be found it seems... I finally used the Start Menu shortcut that seems to have been renewed during the upgrade, and FF started and presented me again with the warning that a blank profile was created.............

All in all, very disrupting user experience.... I don't expect an upgrade to break both my profile and the shortcuts in the taskbar!

Below are the ini files in their current state:

See profiles.ini:

[Install308046B0AF4A39CB]
Default=Profiles/u3jmfcf3.default-release
Locked=1

[Profile2]
Name=default-release
IsRelative=1
Path=Profiles/u3jmfcf3.default-release

[InstallCA9422711AE1A81C]
Default=Profiles/42f4yg73.default
Locked=1

[Profile1]
Name=dev-edition-default
IsRelative=1
Path=Profiles/i2omnq5s.dev-edition-default

[Profile0]
Name=default
IsRelative=1
Path=Profiles/42f4yg73.default
Default=1

[General]
StartWithLastProfile=1
Version=2

[InstallEB854E6297F96212]
Default=Profiles/42f4yg73.default
Locked=1

[Install4D589497A5E2C2E9]
Default=Profiles/42f4yg73.default
Locked=1

installs.ini

[308046B0AF4A39CB]
Default=Profiles/u3jmfcf3.default-release
Locked=1

[CA9422711AE1A81C]
Default=Profiles/42f4yg73.default
Locked=1

[EB854E6297F96212]
Default=Profiles/42f4yg73.default
Locked=1

[4D589497A5E2C2E9]
Default=Profiles/42f4yg73.default
Locked=1

Happy to hear any suggestion on how to fix this.

Update on previous comment: I checked the path to binary for the old and the new shortcuts and they are the same... this is weird and makes no sense, but let's account that on a windows related weirdness.

Other update: starting with the browser window opened as of the end of my previous comment (with the newly created blank profile), I went again to about:profiles, clicked again on "set as default profile" for my old profile 42f4yg73.default, but this time I closed the browser and restarted it from the Start Menu. It started on the correct profile this time (42f4yg73.default).

Here are the ini files as of now:

profiles.ini

[Install308046B0AF4A39CB]
Default=Profiles/42f4yg73.default
Locked=1

[Profile2]
Name=default-release
IsRelative=1
Path=Profiles/u3jmfcf3.default-release

[InstallCA9422711AE1A81C]
Default=Profiles/42f4yg73.default
Locked=1

[Profile1]
Name=dev-edition-default
IsRelative=1
Path=Profiles/i2omnq5s.dev-edition-default

[Profile0]
Name=default
IsRelative=1
Path=Profiles/42f4yg73.default
Default=1

[General]
StartWithLastProfile=1
Version=2

[InstallEB854E6297F96212]
Default=Profiles/42f4yg73.default
Locked=1

[Install4D589497A5E2C2E9]
Default=Profiles/42f4yg73.default
Locked=1

installs.ini

[308046B0AF4A39CB]
Default=Profiles/42f4yg73.default
Locked=1

[CA9422711AE1A81C]
Default=Profiles/42f4yg73.default
Locked=1

[EB854E6297F96212]
Default=Profiles/42f4yg73.default
Locked=1

[4D589497A5E2C2E9]
Default=Profiles/42f4yg73.default
Locked=1

I've also encountered this on two different computers (Mozilla work computer and home computer).

I don't run nightly. I'm on 67 on both. I run Ubuntu 18.04 on both. I do have multiple profiles. I've only experienced the loss of one profile on each of the two computers so far. In both cases I restored the profile from backup.

My profiles.ini file looks like this from my work laptop. Note, this is profiles.ini after the problem where I've not modified the profiles.ini file but have restored the csr6pj5l.gene profile directory from backup

[Install4F96D1932A9F858E]
Default=y96ohtaw.work

[Profile3]
Name=private
IsRelative=1
Path=csr6pj5l.private

[Profile2]
Name=test
IsRelative=1
Path=csr6pj5l.test

[Profile1]
Name=gene
IsRelative=1
Path=csr6pj5l.gene

[Profile0]
Name=work
IsRelative=1
Path=y96ohtaw.work
Default=1

[General]
StartWithLastProfile=1
Version=2

[Profile4]
Name=kalx
IsRelative=1
Path=csr6pj5l.kalx

(In reply to alex_mayorga from comment #18)

¡Hola Dave!

Ended up while researching on the following questions in the Spanish SuMo forums:

https://support.mozilla.org/questions/1259984
https://support.mozilla.org/questions/1260173
https://support.mozilla.org/questions/1260071
https://support.mozilla.org/questions/1260211
https://support.mozilla.org/questions/1260038

FWIW I've requested them all for copies of their ''installs.ini'' and ''profiles.ini'' files.

Thanks however I'd appreciate it if in the future you directed folks to file new bugs, this bug is overloaded and difficult to follow already.

Should this one warrant a dot release perhaps or could it be fixed "automagically"?

If I knew what the problem was I could answer that.

I thought the problem was solved (see Comment 20) but today the issue manifested in a new way:

While I had already one FF window opened using the profile I wanted (42f4yg73.default), I clicked on a hyperlink in another application which started another FF instance (instead of opening the one that was already opened as I would have expected). And this instance decided again to create a new blank profile.

Now the situation looks like this in about:profiles of the newly opened FF instance:

Profile: default
This profile is in use in another application and it cannot be deleted.
Default Profile	no
Root Directory	C:\Users\xxxx\AppData\Roaming\Mozilla\Firefox\Profiles\42f4yg73.default
Local Directory	C:\Users\xxxx\AppData\Local\Mozilla\Firefox\Profiles\42f4yg73.default

Profile: dev-edition-default
Default Profile	no
Root Directory	C:\Users\xxxx\AppData\Roaming\Mozilla\Firefox\Profiles\i2omnq5s.dev-edition-default
Local Directory	C:\Users\xxxx\AppData\Local\Mozilla\Firefox\Profiles\i2omnq5s.dev-edition-default

Profile: default-release
Default Profile	no
Root Directory	C:\Users\xxxx\AppData\Roaming\Mozilla\Firefox\Profiles\u3jmfcf3.default-release
Local Directory	C:\Users\xxxx\AppData\Local\Mozilla\Firefox\Profiles\u3jmfcf3.default-release

Profile: default-release-1
This is the profile in use and it cannot be deleted.
Default Profile	yes
Root Directory	C:\Users\xxxx\AppData\Roaming\Mozilla\Firefox\Profiles\lqdpxhif.default-release-1
Local Directory	C:\Users\xxxx\AppData\Local\Mozilla\Firefox\Profiles\lqdpxhif.default-release-1

In the about:profiles of the instance I was using, it just says Another copy of Firefox has made changes to profiles. You must restart Firefox before making more changes.

The previous situation was as of Comment 20.

You can see that yet another profile was created (default-release-1)!

Here are the ini files:

profiles.ini

[General]
StartWithLastProfile=1
Version=2

[Install308046B0AF4A39CB]
Default=Profiles/42f4yg73.default
Locked=1

[Profile2]
Name=default-release
IsRelative=1
Path=Profiles/u3jmfcf3.default-release

[Install9DED23DF4360B491]
Default=Profiles/lqdpxhif.default-release-1
Locked=1

[Profile1]
Name=dev-edition-default
IsRelative=1
Path=Profiles/i2omnq5s.dev-edition-default

[Profile0]
Name=default
IsRelative=1
Path=Profiles/42f4yg73.default
Default=1

[InstallCA9422711AE1A81C]
Default=Profiles/42f4yg73.default
Locked=1

[Profile3]
Name=default-release-1
IsRelative=1
Path=Profiles/lqdpxhif.default-release-1

[InstallEB854E6297F96212]
Default=Profiles/42f4yg73.default
Locked=1

[Install4D589497A5E2C2E9]
Default=Profiles/42f4yg73.default
Locked=1

installs.ini

[308046B0AF4A39CB]
Default=Profiles/42f4yg73.default
Locked=1

[9DED23DF4360B491]
Default=Profiles/lqdpxhif.default-release-1
Locked=1

[CA9422711AE1A81C]
Default=Profiles/42f4yg73.default
Locked=1

[EB854E6297F96212]
Default=Profiles/42f4yg73.default
Locked=1

[4D589497A5E2C2E9]
Default=Profiles/42f4yg73.default
Locked=1

You can compare them to the ones in Comment 19 and 20.

Hum after investigating the linked bugs on bugzilla, what I experienced in Comment 23 seems somewhat similar to Bug 1553815 which was "resolved" as invalid even when the arguments from the FF developer don't make sense from user point of view (when I click a link in another application, and I already have one FF instance opened, user expect the link to open in that instance!!

And in my case, the FF instance that was already opened is not even a non-default profile, since I explicitly asked FF (as of Comment 20) to set 42f4yg73.default as default profile (by clicking "set as default profile" in about:profiles).

The main issue here is that FF should respect that choice and not continue creating default-release-X profiles each time it is launched!

Zertrin, I may have encountered a problem similar to yours at an user's PC. His problem is when double-clicking the Firefox icon can open the default profile. However, linking or opening html files through other applications will use the new profile. Even if profile.ini and install.ini are reset, a new profile will be created automatically.

I directed him to remove the unused profiles and enter the default application settings for Windows. (He is using win10) Set default browser here to other such as Microsoft edge. Then I found there is no longer firefox option in default browser settings.

I think the problem is the default browser setting in windows is not the firefox he currently using for some reason. Previously, this user had installed other versions of Firefox, but it has been uninstalled, and there is only one in control panel. The problem is in the registry. Since I haven't been able to communicate more deeply. It seems we could get some information from the settings of HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\Shell\Associations\URLAssociations(http|https)\UserChoice.

However, the registry will be reset by the overlay installation as I know. I directly let this user download the latest version to overwrite. Then set the default browser and the issue is resolved.

(In reply to yxu from comment #25)

I directed him to remove the unused profiles and enter the default application settings for Windows. (He is using win10) Set default browser here to other such as Microsoft edge. Then I found there is no longer firefox option in default browser settings.

For me the "Mozilla Firefox" choice is still available in the default application settings for Windows and ...

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\Shell\Associations\URLAssociations(http|https)\UserChoice

... is set to FirefoxURL as normally expected

Furthermore, HKEY_CLASSES_ROOT\FirefoxURL\shell\open\command is set to "C:\Program Files\mozilla firefox\firefox.exe" -osint -url "%1"

Ok, I apologize I really should have closed this bug as soon as it was opened. It has ended up being a catch-all for many people with different environments and so it has become nearly impossible to follow what is happening for who.

For Windows users it is probable that you're hitting bug 1555319. I'd appreciate it if you would avoid adding "me too" or "not my problem" comments there, that bug is well understood and it just needs to be fixed.

On Linux we've found that some distributions install every version of Firefox (not channel, version!) into different installation directories which will trigger this issue.

For other cases we're having difficulty figuring out what is going wrong here. Obviously we haven't reproduced this problem during the fairly extensive testing that we did on this feature. If someone is able to come up with some steps to reproduce this or otherwise has their system in a state where the new profile has been created and then hasn't made any modifications to their profiles (particularly hasn't switched back to the old profile or used it with any other install) then please file a new bug and CC me.

I'm sorry I can't offer much more right now.

:mossop

On Linux we've found that some distributions install every version of Firefox (not channel, version!) into different installation directories which will trigger this issue.

Can you share either which distributions/versions of Linux you've seen do this, or a link to where that info is, or a way to detect if our distro/version of Linux is doing this?

If someone is able to come up with some steps to reproduce this or otherwise has their system in a state where the new profile has been created and then hasn't made any modifications to their profiles (particularly hasn't switched back to the old profile or used it with any other install) then please file a new bug and CC me.

If it really can't be reproduced I can

  • Spin up a VM of Ubuntu 18.04
  • Downgrade firefox to pre 67
  • Restore from backup my pre Firefox 67 profile into the VM
  • Upgrade firefox

I would expect that this would work with any profile (since it affected two different computers of mine) but if that's not the case and there's some special sauce in my profiles, let me know and I can go through this sequence (I don't want to unless it's needed) to reproduce it

Flags: needinfo?(dtownsend)

(In reply to Gene Wood [:gene] from comment #28)

:mossop

On Linux we've found that some distributions install every version of Firefox (not channel, version!) into different installation directories which will trigger this issue.

Can you share either which distributions/versions of Linux you've seen do this, or a link to where that info is, or a way to detect if our distro/version of Linux is doing this?

If someone is able to come up with some steps to reproduce this or otherwise has their system in a state where the new profile has been created and then hasn't made any modifications to their profiles (particularly hasn't switched back to the old profile or used it with any other install) then please file a new bug and CC me.

If it really can't be reproduced I can

  • Spin up a VM of Ubuntu 18.04
  • Downgrade firefox to pre 67
  • Restore from backup my pre Firefox 67 profile into the VM
  • Upgrade firefox

I would expect that this would work with any profile (since it affected two different computers of mine) but if that's not the case and there's some special sauce in my profiles, let me know and I can go through this sequence (I don't want to unless it's needed) to reproduce it

That would be much appreciated (I'd make sure and clear any profiles before you restore your profiles in there). Even if there is something special about your profiles I'd love to know that. If you wanted to avoid a back and forth and you were willing to share those backed up profiles with me then I could just try to reproduce myself and it'd probably mean I'd track the issue down faster. removing the bookmarks/history beforehand shouldn't affect things.

Flags: needinfo?(dtownsend)

:mossop and I chatted outside the ticket and it sounds like what I'm experiencing is distinct from what this ticket is talking about. Symptoms which I'm getting which deviate from this ticket are

  • Loss of all tabs except 2 of 5 pinned tabs
  • Bitwarden stops working and has to be uninstalled, reinstalled, logged in, logged out, uninstalled, reinstalled, logged in
  • The problem has occurred on two computers, each on a single profile. It's occurred twice on one of those computers now.
  • I don't get the "Important News" dialog box about downgrade
  • No new profile is created (merely one of my profiles gets affected in the way described here

This happened to me. Windows 10, only one install of regular firefox on my system.

Upon closer inspection, I actually do have two installations of Firefox on my PC... Program Files and Program Files (x86), however they both identify themselves as 67.0 (64-bit). I don't know how this came to be. To my knowledge I have only installed Firefox once... immediately after the OS was installed.

Closing this per comment 29, if folks are having issues not listed there and can provide the information listed there then please file a new bug.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INCOMPLETE

I had the same problem like the poster of the first reddit thread, but in my case it happened after upgrading from Fedora29 to Fedora30. I solved the issue by deleting the compatibility.ini in my old profile. As it turned out while being the exact same version of Firefox (67.0-4), the one of Fedora29 was built a little bit after the one of Fedora30 and thus the Build ID that was in the LastVersion=67.0_20190523144739/20190523144739 line in the compatability.ini file of my profile was higher/newer than the one of the currently installed Firefox (Build ID 20190523132402 according to about:support).
Deleting compatibility.ini Firefox let me use my old profile again.

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:67.0) Gecko/20100101 Firefox/67.0
openSuse leap 15.0

After updating from 66 to 67 i get no problem launching FF

Steps to reproduce:

i launch FF with "firefox --safe-mode" to make test
then
i close FF
then
i launch FF with "firefox"

Actual results:

i get a message "using an older version of firefox can corrupt bookmarks..." with buttons "quit" and "create a new profile"
then
i quit
then
i launch "firefox -P" and choose "default"
then
i get again "using an older version of firefox can corrupt bookmarks..." with buttons "quit" and "create a new profile"
then
i launch FF with "MOZ_ALLOW_DOWNGRADE=1 firefox -P"
then
i get my default profile with my default settings
then
i close FF
then
i launch FF
no more problem

Happily there is a workaround but this is a true bug.

Blocks: 1557125
Has Regression Range: --- → yes
You need to log in before you can comment on or make changes to this bug.