Comment 61 for bug 31746

I second this, the current behavior when running multiple profiles is just plain broken and confusing. Command line options shouldn't act completly different depending on if an application is already running. And the workaround of "-no-remote" doesn't really fix this issue, as the intended behavior of:

"firefox -P MyProfile http://www.example.org"

should be:

1) If no Firefox is running, launch one using MyProfile opening http://www.example.org
2) If Firefox with MyProfile is already running, open a new window of it displaying http://www.example.org
3) If only a Firefox with a different profile is already running, ignore it and act as in 1)

-no-remote gives you 1) and 3), but gives you a:

"Firefox is already running, but is not responding. To open a new window, you must first close the existing Firefox process, or restart your system."

error message on 2).

And having "firefox -ProfileManager" just open a new window and not showing the ProfileManger really can't be considered the right behavior, as its so obviously wrong.

On top of that "-a" and "-no-remote" are really just ugly implementation details that shouldn't be required to simply run two profiles at the same time.