Obsidian on Ubuntu 24.04 creating new Firefox profile instead of using system-default

Steps to reproduce

On Ubuntu 24.04 LTS, using the Snap install of Obsidian, click on an external link in Obsidian (formatted as [link](``http://link.com``)) .

Did you follow the troubleshooting guide? [Y/N]

Yes. This same result occurs in the Sandbox vault.

Expected result

The external link would open in the system-default Firefox profile located in home/$USER/.config/mozilla/firefox/$profilestring.default-release or similar.

Actual result

Obsidian opens the link in a new Firefox profile that is located in the Obsidian snap directory, not the system-default Firefox profile.

The Firefox profile’s location can be verified in Firefox’s own about:profiles page, and it identifies the active Firefox profile as existing in /home/$USER/snap/obsidian/62/.config/mozilla/firefox/$profilestring.default-release.

It has effectively recreated the ‘standard’ Firefox Profile folder structure (seen above) as a subfolder within its own folder structure. The same Firefox executable is being executed on (I have no other installations of Firefox on this machine), but the location of the Firefox Profile it is looking for is incorrect.

Environment

Ubuntu 24.04 LTS, using GNOME. Installation of Obsidian is through the default Snap repository.

I am using an apt installation of Firefox, not the default installation option for Firefox on Ubuntu (which uses a Snap). This has not caused any problems with other applications.


Additional information

I find this extremely odd behavior and I cannot seem to get Obsidian to “understand” that the Firefox profile it wants is in the default location, not within its own local folder.

I have tried to manually delete/rename the mozilla folder located in the Snap folder, but upon clicking on a link again it would simply recreate the folder & thus Firefox profile.

Using the community plugin “Open Link With” makes no difference. Obsidian will recreate a new, empty Profile within its own local folder structure regardless.

If this is a problem specific to Snap installations of Obsidian, this would make some amount of sense to me – I have not tried installing Obsidian as a standard (i.e. non-Snap) application in Ubuntu.