[magicalhippo]

Actually I realized I totally forgot a crucial detail. I run my other profile using Firefox Beta, so they really are separate applications. I assume that would fully explain why they behave separately. Sorry about that.

Will have to test using multiple profiles using the same executable.

However, if the same "trick" works on Linux, perhaps it could be exploited by Firefox creating a separate executable that launches a specific profile.

We do that with our application, using the "self-extracting zip trick", ie appending data to the executable that is read during start-up.

[mjevans]

Firefox couldn't do the link thing itself without either being a setuid binary, or running somewhere the user could replace Firefox. You could MAYBE get it to make a symlink under XDG_RUNTIME_DIR, or /tmp if that's unset, since symlinks work across devices. At least on my desktop /tmp is allowed to contain executables and a symlink to /usr/bin/bash executes and remains named as the symlink path.

Though it'd still be many times better if Firefox made it easier to tell which profile was associated with a given process (prefix the argument list as if launched with that). ALSO if KDE's task list supported improved flexibility for group categorization. It wouldn't even need to run an external program other than once for each new window created.