Version info: I'm using up-to-date Nightly 106. I was able to get back to a working state by manually editing my desktop Nightly shortcut, to set the `Target` value to `"path/to/firefox.exe" -ProfileManager` (instead of just `"...firefox.exe"`). This let me launch the profile manager so that I could create a new default profile. But we should probably add some more user-discoverable route to get back to a working state here which doesn't require knowing how to do that.
Bug 1791202 Comment 1 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Version info: I'm using up-to-date Nightly 106. I was able to get back to a working state by manually editing my desktop Nightly shortcut, to add `-ProfileManager` at the end of the `Target` field, so that it says `"path/to/firefox.exe" -ProfileManager`. This let me launch the profile manager so that I could create a new default profile. But we should probably add some more user-discoverable route to get back to a working state here which doesn't require knowing how to do that.
Version info: I'm using up-to-date Nightly 106. I was able to get back to a working state by manually editing my desktop Nightly shortcut, to add `-ProfileManager` at the end of the `Target` field, so that it says `"path/to/firefox.exe" -ProfileManager`. This let me launch the profile manager so that I could create a new default profile. But we should probably add some more user-discoverable route to get back to a working state here which doesn't require knowing how to do that. Otherwise users just end up with Firefox being indefinitely non-functional with no clear way to recover (other than maybe (?) an uninstall+reinstall loop).