1997400 - Deleting a specific selectable profile shows a blank page

Status: RESOLVED DUPLICATE of bug 2000125

(Toolkit :: Startup and Profile System, defect)

Description

[Duncan McIntosh [:dmcintosh]]

Attachment: firefox_147xZr3Cu7.mp4

I have two profiles in my Nightly install: one named 'Original profile', which is where all my bookmarks/etc. are, and one named 'Testing Ground' that I don't really cannot use.

I'd like to delete 'Testing Ground', especially since bug 1990634 landed and I'd like to test FxBackup things.

Steps (starting from 'Original profile'):

1. Click on the hamburger icon → 'Original profile' → 'Manage profiles'.
2. Click on the trash can icon next to 'Testing Ground'.

Expected: Firefox opens a window in Testing Ground that shows me what data I'll lose, etc. so I can agree to delete it.

Actual: Firefox opens a window without any profile? that has about:deleteprofile open. The page contents are blank. Opening the browser log and selecting 'Multiprocess' shows:

TypeError: can't access property "toContentSafeObject", (intermediate value).currentProfile is null ProfilesParent.sys.mjs:392:11

This only seems to happen with 'Testing Ground' — I made a new one called 'other' and that deleted as normal. I also can't open 'Testing Ground' to use normally, since it also opens with no selected profile in that case. I don't remember when I made 'Testing Ground', but it was a while ago (I'd guess August to September sometime?)

Possible/probable that my profile's corrupted somehow, but I'd still like to know how to delete it!

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The severity field is not set for this bug.
:mossop, could you have a look please?

For more information, please visit BugBot documentation.

Comment 2

[Dave Townsend [:mossop]]

In the problem profile in about:config what is the value of browser.profiles.enabled and toolkit.profiles.storeID and then what is the value of toolkit.profiles.storeID for the other profile?

Comment 3

[Duncan McIntosh [:dmcintosh]]

In 'Original profile' (working):

• browser.profiles.enabled = true
• toolkit.profiles.storeID = 7f2edf3e

In 'Testing Ground' (not working):

• browser.profiles.enabled = true
• toolkit.profiles.storeID = 86a8ca1d

...which is weird, since the UI in 'Testing Ground' doesn't seem to show the Profiles button at all? (And about:deleteprofile is still blank.)

Comment 4

[Dave Townsend [:mossop]]

(In reply to Duncan McIntosh [:dmcintosh] from comment #3)

In 'Original profile' (working):

• browser.profiles.enabled = true
• toolkit.profiles.storeID = 7f2edf3e

In 'Testing Ground' (not working):

• browser.profiles.enabled = true
• toolkit.profiles.storeID = 86a8ca1d

...which is weird, since the UI in 'Testing Ground' doesn't seem to show the Profiles button at all? (And about:deleteprofile is still blank.)

Ok so the storeID in the non-working profile is incorrect. I already have a patch in progress to help with this so I'm going to dupe to the bug where I'm working on it. Do you have any idea how that might have gotten changed. Did you manually edit the profile's prefs in some way or anything?

Comment 5

[Duncan McIntosh [:dmcintosh]]

Thanks for looking into it, and hopefully the fix goes well!

Not sure why the pref would change, I've probably fiddled with some prefs but nothing relating to profiles. Only thing I can think of is that I have a handful of toolkit profiles, mostly from trying to install Release/Beta but also probably for development, but that shouldn't impact anything? ('release', 'firstgen' (that's the one that I use, with the selectable profiles), 'default-release', 'default-release-1', 'unbroken', 'profile-default', 'default-release-2')