Sorry for the 3 years late answer, I became interested in this topic just now and found this question.
I didn't find a documented solution anywhere, so I checked out the source code and here is a very relevant part:
http://dxr.mozilla.org/mozilla-central/source/toolkit/xre/nsAppRunner.cpp#1537
Here, the nullptr at the end of the line unfortunately means that the profile argument is not being passed to the SendCommandLine function, therefore it's not possible to select the correct firefox window to send the openurl message to.
However, we see that the username is being passed and that the username is being intiailized from the LOGNAME environment variable. Based on this, I came up with the following solution:
- I wrap firefox with this script, called firefox.sh:
FOX_PROFILE=facebook
export LOGNAME=errge.$FOX_PROFILE
/opt/firefox/firefox -profile ~/.mozilla_profiles/$FOX_PROFILES "$@"
when ran the first time, it starts a new instance and the ~/.mozilla_profiles/facebook directory has to exist,
when ran the second time if the facebook profile is already running, it correctly connects to it,
it can send commands correctly to multiple different running profiles (of course you have to change the FOX_PROFILE parameter in the first line in the different scripts).
I tested this with Firefox 26 on Linux and it works.
Alternatively, here is my full-fledged solution that you may want or not want to use:
#!/bin/bash
set -e
FOX=/opt/firefox/firefox
MESSAGE=$@
if [ -z "$FOX_PROFILE" ]; then
if [ -z "${MESSAGE}" ]; then
FOX_PROFILE=default
else
FOX_PROFILE=$(kdialog --default default --menu "-- ${MESSAGE} --" default default google google facebook facebook errge errge spam spam)
fi
fi
export FOX_PROFILE
# This hack is needed, because firefox remote command line sending
# ignores the profile parameter. See nsAppRunner.cpp:1505.
export LOGNAME=errge.$FOX_PROFILE
# Using background execution instead of exec, so the behavior is
# consistent when the profile is already running and when it's just
# starting up.
$FOX -profile ~/.mozilla_profiles/$FOX_PROFILE "$@"
# Huge success.
exit 0
If you run the script without any parameter, it autoselects the default profile, but you can override it by setting FOX_PROFILE by hand in your shell. If an URL is passed in the command line, it always asks for a profile in which to open it, this is because I mainly click through from my chat and email program and in those case I want to always select a profile (google for calendar spam, facebook for birthday spam, etc.). Of course you can change the logic to fit your style of usage, this is just an example, the important knowledge is the LOGNAME trick.
And of course you have to make sure that this wrapper script is the only way to start the browser on your machine. Because if you open a profile without the correct LOGNAME set, than you won't be able to communicate to that profile anymore. I put this script as first in my path via multiple symlinked names, like x-www-browser, firefox, sensible-browser and put it in the BROWSER environment variable too. How to do this exactly depends on your GNU/Linux distribution.
Best Answer
This is because Firefox uses some sort of locking mechanism so that only one Firefox process can access each profile, and I think that's to avoid corruption in the sqlite databases (places, bookmarks, history, etc).
If you start Firefox with -no-remote, it claims exclusive access to the profile ("default" in your case) and no other Firefox process can use it, even if the second instance is invoked without the -no-remote.
You can of course use Ctrl+N or File > New Window to create a new window from within Firefox.
The proper way around this is to run Firefox 4 with -no-remote, and invoke your Fx3.6 instances without that flag.