Closed Bug 2067585 Opened 1 month ago Closed 1 month ago

about:editprofile and about:deleteprofile show as blank pages for all secondary profiles despite these profiles showing up in about:profilemanager.

Categories

(Toolkit :: Startup and Profile System, defect)

Product:
Toolkit
Component:
Startup and Profile System
Version:
Firefox 154
Type:
defect

Tracking

()

Status:
RESOLVED DUPLICATE of bug 2013849

People

(Reporter: mozbugzilla, Unassigned)

Details

Duplicate of closed bug 2029618. I have the exact same situation but no workaround.

Steps to reproduce:

  1. Create a new profile. New window opens
  2. Choose "Edit this profile"

Actual results:

'about:newprofile' and 'about:deleteprofile' show as blank.

Expected results:

Should have opened the about:editprofile and about:deleteprofile pages which I can see on my ooooold main profile. I am able to do this on my default profile. Same as original poster.

These are are errors showing up in the browser console (app menu -> more tools -> browser console)

TypeError: can't access property "toContentSafeObject", currentProfile is null ProfilesParent.sys.mjs:42:7
TypeError: can't access property "toContentSafeObject", currentProfile is null ProfilesParent.sys.mjs:42:7
TypeError: can't access property "toContentSafeObject", currentProfile is null ProfilesParent.sys.mjs:42:7
TypeError: can't access property "toContentSafeObject", (intermediate value).currentProfile is null ProfilesParent.sys.mjs:171:11
Uncaught (in promise) TypeError: can't access property "theme", SelectableProfileService.currentProfile is null
    _onPanelShowing chrome://browser/content/browser-profiles.js:120
3 browser-profiles.js:120:32
TypeError: can't access property "toContentSafeObject", currentProfile is null ProfilesParent.sys.mjs:42:7
Content-Security-Policy: 'unsafe-eval' oder 'wasm-unsafe-eval' innerhalb "script-src-elem" wird ignoriert. Unexpected_type
Summary: about:editprofile and about:deleteprofile show as blank pages for all secondary profiles despite this profile showing up in about:profilemanager. → about:editprofile and about:deleteprofile show as blank pages for all secondary profiles despite these profiles showing up in about:profilemanager.

(In reply to Benjamin from comment #0)

Duplicate of closed bug 2029618. I have the exact same situation but no workaround.

Steps to reproduce:

  1. Create a new profile. New window opens

How did you create the new profile?

Flags: needinfo?(mozbugzilla)

(In reply to Dave Townsend [:mossop] from comment #2)

How did you create the new profile?
In the main profile, clicking on "mainprofilename > Create a New Profile"

Flags: needinfo?(mozbugzilla)

I also just tested this on a fresh "user profile" instance firefox -P --no-remote: Same effect. Seems to be environment related. I'm on

  • Ubuntu 26.04
  • Dark theme (Firefox appears in dark theme on start)
  • German locale

Interestingly I cannot even delete this new user profile instance as Firefox asks me to delete the profiles first. Which I'm unable to do ;-)

Enter about:config into the address bar and search for devtools.chrome.enabled and make sure it is set to true. Then in the browser console enter the following and then paste the output in here:

Services.dirsvc.get("ProfD", Ci.nsIFile).path

Then do the same for this:

await SelectableProfileService.getAllProfiles().then(ps => ps.map(p => p.path))

Flags: needinfo?(mozbugzilla)
Services.dirsvc.get("ProfD", Ci.nsIFile).path
"/home/ben/.mozilla/firefox/np7o6eki.vanilla-temp"

await SelectableProfileService.getAllProfiles().then(ps => ps.map(p => p.path))
Array(3) [ "/home/ben/.mozilla/firefox/np7o6eki.vanilla-temp", "/home/ben/.mozilla/firefox/WiCbNnTP.Profil 1", "/home/ben/.mozilla/firefox/9Uz8psJr.Profil 2" ]
​
0: "/home/ben/.mozilla/firefox/np7o6eki.vanilla-temp"
​1: "/home/ben/.mozilla/firefox/WiCbNnTP.Profil 1"
​2: "/home/ben/.mozilla/firefox/9Uz8psJr.Profil 2"
​length: 3
​<prototype>: Array []
​<global>: SystemGlobal { crypto: Crypto, indexedDB: IDBFactory, locks: LockManager, … }

(In reply to Dave Townsend [:mossop] from comment #5)

Just did the same in "Profil 1". And then tried to access about:editprofile which produced a different kind of error

Services.dirsvc.get("ProfD", Ci.nsIFile).path
"/srv/private/Anwendungsdaten/firefox/WiCbNnTP.Profil 1"

await SelectableProfileService.getAllProfiles().then(ps => ps.map(p => p.path))
Array(3) [ "/home/ben/.mozilla/firefox/np7o6eki.vanilla-temp", "/home/ben/.mozilla/firefox/WiCbNnTP.Profil 1", "/home/ben/.mozilla/firefox/9Uz8psJr.Profil 2" ]
​0: "/home/ben/.mozilla/firefox/np7o6eki.vanilla-temp"
​1: "/home/ben/.mozilla/firefox/WiCbNnTP.Profil 1"
​2: "/home/ben/.mozilla/firefox/9Uz8psJr.Profil 2"
​length: 3
​<prototype>: Array []
​<global>: SystemGlobal { crypto: Crypto, indexedDB: IDBFactory, locks: LockManager, … }

Uncaught (in promise) TypeError: can't access property "theme", SelectableProfileService.currentProfile is null
    _onPanelShowing chrome://browser/content/browser-profiles.js:120
    init chrome://browser/content/browser-profiles.js:52
    dispatchCustomEvent moz-src:///browser/components/customizableui/PanelMultiView.sys.mjs:296
    dispatchCustomEvent moz-src:///browser/components/customizableui/PanelMultiView.sys.mjs:1708
    _blockersPromise moz-src:///browser/components/customizableui/PanelMultiView.sys.mjs:331
browser-profiles.js:120:32
TypeError: can't access property "toContentSafeObject", currentProfile is null ProfilesParent.sys.mjs:42:7
Flags: needinfo?(mozbugzilla)

(In reply to Benjamin from comment #7)

(In reply to Dave Townsend [:mossop] from comment #5)

Just did the same in "Profil 1". And then tried to access about:editprofile which produced a different kind of error

Services.dirsvc.get("ProfD", Ci.nsIFile).path
"/srv/private/Anwendungsdaten/firefox/WiCbNnTP.Profil 1"

That /srv/private/Anwendungsdaten/firefox is a bit surprising. Do you have some kind of symlink set up between that and /home/ben/.mozilla/firefox, or vice versa?

Flags: needinfo?(mozbugzilla)

(In reply to Dave Townsend [:mossop] from comment #8)

That /srv/private/Anwendungsdaten/firefox is a bit surprising. Do you have some kind of symlink set up between that and /home/ben/.mozilla/firefox, or vice versa?

Yes. /srv/private is the backed up, ZRAID1, rotating metal location for my private data. Sorry for the confusion.

lrwxrwxrwx     1 ben  ben      28 Jun  8  2024 Anwendungsdaten -> /srv/private/Anwendungsdaten
Flags: needinfo?(mozbugzilla)

To complete the picture:

$ ls -la .mozilla
total 72
drwx------  5 ben ben   6 Aug 12 20:48 ./
drwxr-x---+57 ben ben 114 Aug 31 00:33 ../
drwx------  2 ben ben   2 Feb 27  2021 extensions/
lrwxrwxrwx  1 ben ben  36 Jan 16  2017 firefox@ -> /srv/private/Anwendungsdaten/firefox
drwxr-xr-x  2 ben ben   5 Aug 22 18:56 native-messaging-hosts/
drwx------  2 ben ben   2 Feb 27  2021 systemextensionsdev/

Ok so this is basically the same as bug 2013849 which for some reason I couldn't reproduce the last I tried but I will try again.

Status: UNCONFIRMED → RESOLVED
Closed: 1 month ago
Duplicate of bug: 2013849
Resolution: --- → DUPLICATE

(In reply to Dave Townsend [:mossop] from comment #11)

Ok so this is basically the same as bug 2013849 which for some reason I couldn't reproduce the last I tried but I will try again.

Thank you Dave, for the immediate debugging support and quickly spotting the root cause!

You need to log in before you can comment on or make changes to this bug.