Closed hiredman closed 5 years ago
and now that I got the flatpak firefox to launch, when I try open my non-flatpak, default profile it just opens new windows in the flatpak browser.
I guess what I really want is some kind of --isolate-this-firefox-process-and-dont-punch-holes-in-the-isolation-so-firefox-can-pretend-it-isnt-isolated flag, and maybe a --you-are-a-unique-snowflake-firefox-process-so-dont-ever-respond-to-someone-lauching-firefox-outside-of-your-container-and-definitely-dont-create-a-new-window-for-a-process-outside-of-your-container flag
I constantly have to update how I am launching the flatpak to get it to open a profile other then the default.
For a while I could just pass in an argument and it would work, but some change to the launcher script broke that. Then I symlinked the default profile directory to the profile I wanted to use inside the flatpak container or whatever and that worked for a while. Most recently even with the symlink launching firefox nightly via flatpak just opens a new window for my non-nightly non-flatpak firefox browser.