1722865 - Second Firefox profile is not automatically created after the first profile was deleted

Status: NEW

(Toolkit :: Startup and Profile System, defect)

Description

[Catalin Sasca, Desktop Test Engineering [:csasca]]

Attachment: no new profile created.gif

Affected versions

• 92.0a1 (2021-07-28) MSIX installer

Affected platforms

• Windows 11

Preconditions

• Have default regular Firefox profiles created first

Steps to reproduce

1. Install MSIX build and launch it to create a new profile then close Firefox
2. Open a regular Firefox build and access about:profiles
3. Look for the msix created profile and select remove - delete files
4. Launch the msix Firefox build

Expected result

• A new profile is created automatically and Firefox is launched

Actual result

• The profile manager is launched

Regression range
Not a regression, msix package affected

Additional notes

• The issue can be seen in the attachment

Comment 1

[Nick Alexander :nalexander [he/him] (PTO Feb 24-March 3)]

This is interesting. My guess is that this is not MSIX specific. I think we should add this as an item for testing with :mhowell's patch for Bug 1709969.

NI to Molly just so she's aware of this potential issue.

Comment 2

[Molly Howell (she/her) (mostly inactive)]

I can reproduce this on a non-MSIX build, yes.

I think I may know what's happening. The implementation of the remove button in about:profiles (which is this profile service function) doesn't seem to have been made aware of dedicated profiles; along with the profile's directory, it removes the profile's old-style Profile* section in profiles.ini, but it does not remove the profile's Install* section or its entry in installs.ini. Manually removing those two sections does lead to the expected behavior of a new profile being created during the next startup of the affected build, instead of the profile manager appearing.

This is not an MSIX-related bug, and I don't think it's serious enough to block shipping the MSIX, so I'm removing this bug's dependency relationships and moving it to the appropriate component.

Comment 3

[Dave Townsend [:mossop]]

I think this bug will have existed since at least bug 1518587, possibly even further back.