Closed Bug 1736618 Opened 1 year ago Closed 1 year ago

Your Firefox profile cannot be loaded. It may be missing or inaccessible.

Categories

(Toolkit :: Startup and Profile System, defect)

x86_64
Windows 10
defect

Tracking

()

RESOLVED DUPLICATE of bug 1551773

People

(Reporter: serg, Unassigned)

Details

User is unable to use Firefox when profile folder is removed.

STR:

  1. Install Firefox from Microsoft Store (probably same for regular distribution)
  2. Open it so profile is created
  3. Close Firefox
  4. Delete C:\Users\<username>\AppData\Local\Mozilla\Firefox\Profiles\<profile folder>
  5. Delete C:\Users\<username>\AppData\Roaming\Mozilla\Firefox\Profiles\<profile folder>
  6. Open Firefox

Actual result:

Dialog "Your Firefox profile cannot be loaded. It may be missing or inaccessible." with only one button OK that closes the app.

Expected result:

Dialog with some extra button to create a new profile (or select other existing profile).

I don't think there's anything particularly MSIX-specific about this; it's pretty easy to confuse Firefox about the state of the profile configuration. Given how unusual deleting these profiles in this manner will be, I'm marking this as S3. If there's a more common sequence of actions that will result in users find themselves in this situation, let's re-evaluate.

Severity: -- → S3

The Bugbug bot thinks this bug should belong to the 'Toolkit::Startup and Profile System' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Component: Untriaged → Startup and Profile System
Product: Firefox → Toolkit
Component: Startup and Profile System → Installer
Product: Toolkit → Firefox

Yes, this bug does not have to do with MSIX package. I could reproduce it with a regular build.

No longer blocks: msix-packaging
Component: Installer → Startup and Profile System
Product: Firefox → Toolkit
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.