Linux Power-User Narrows Firefox Profile Struggle to Single Set of .desktop Files
The concrete action involves using custom `.desktop` files to force Linux to treat multiple Firefox profiles as completely separate applications. This process is shown to function regardless of whether the user is running a standard Firefox installation or a Flatpak build.
cm0002 drives the argument, insisting the goal is replicating the distinct, separate-app feel of macOS. The technical fix demands embedding specific profile paths, such as `--profile "/home/USERNAME/.var/app/org.mozilla.firefox/config/mozilla/firefox/personal"`, directly into the `Exec=` lines. novafunc provides the necessary blueprints, detailing the required `[Desktop Entry]` and `[Desktop Action]` structures to make the system recognize these profiles.
The community consensus solidifies around this technical blueprint. The single actionable truth is the deployment of properly structured `.desktop` files to bypass system confusion and launch isolated instances. There is no debate on the method; the focus is purely on accurate implementation details.
Key Points
#1The objective is profile isolation, making multiple Firefox instances look like separate apps.
cm0002 stated this requirement explicitly, aiming to mimic the macOS user experience.
#2The mechanism must be a set of custom `.desktop` files.
This was the consensus technical solution provided by both guiding sources.
#3The solution must handle profile pathing correctly for executables.
cm0002 highlighted the necessity of using parameters like `--profile "/path/to/profile"` within the executable call.
#4The structure requires advanced markup for full functionality.
novafunc specified that the necessary entries include both `[Desktop Entry]` and `[Desktop Action]` sections for proper window handling.
Source Discussions (3)
This report was synthesized from the following Lemmy discussions, ranked by community score.