2013849 - currentProfile is null despite the profile being in the database on a system where /home is a symlink

Status: NEW

(Toolkit :: Startup and Profile System, defect)

Description

[Dave Townsend [:mossop]]

Krosylight reported that the new profiles system was non-functional and the error console shows multiple errors about SelectableProfileService.currentProfile being null. We did some diagnosis, the profiles.ini storeID matches the pref, the database lists two profiles one of which appears as /home/krosylight/.mozilla/firefox/TKjQnf6Y.Profile 1 however the directory service actually reports the profile directory as being /var/home/krosylight/.mozilla/firefox/TKjQnf6Y.Profile 1. On Fedora /home is a symlink to /var/home.

Looking through the init I'm not sure that the symlink is the sole issue but we can at least test this easily to see if it reproduces.

Comment 1

[Dave Townsend [:mossop]]

Krosylight was also running this in Flatpak which may be relevant

Comment 2

[Kagami Rosylight 🏳️‍🌈🏳️‍⚧️ [:saschanaz] (they/them)]

FWIW the firefox profiler fails to load the profile after recording possibly because of this.

Comment 3

[BugBot [:suhaib / :marco]]

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

For more information, please visit BugBot documentation.