User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:126.96.36.199) Gecko/20060731 Ubuntu/dapper-security Firefox/188.8.131.52
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:184.108.40.206) Gecko/20060731 Ubuntu/dapper-security Firefox/220.127.116.11
I have three profiles, let's call them "default", "user", and "anon".
What I would expect to happen is that "firefox -P someprofile" makes sure that there is exactly one firefox process running for profile "someprofile" and then opens a new window for the browser running with that profile.
Well, that's not what happens.
"firefox -P default" always seems to open a new window in whatever firefox is already running, even if it's running a different profile. When choosing "default" through the profile manager, however, the "default" profile behaves like "user".
"firefox -P user" starts a new firefox process for profile "user" if one isn't already running and opens a window. But if one is already running, it complains that I "first need to quit" the running firefox process and then doesn't start up a new one.
(The firefox developers should probably also rethink how firefox works in a distributed X11 environment, where multiple instances of firefox may be using the same X11 display but running on different hosts and even as different users.)
Steps to Reproduce:
Create multiple profiles, then try to start them up with "firefox -P something" and "firefox -ProfileManager".
Sometimes opens windows for the wrong profile, sometimes refuses to start up firefox (see above).
The profiles should behave as if each of them were the default profile for a single-profile user; they just happen to share the same display.
I can reproduce some of this with Mozilla/5.0 (X11; U; Linux i686; en-US; rv:18.104.22.168) Gecko/0000000000 Firefox/22.214.171.124 (Ubuntu-edgy).
Using the "firefox -P <profile>" syntax, I can open a new browser window for each profile if one is not already running. If one is already running for that profile, I get a dialog box that says:
"Firefox is already running, but it is not responding. To open a new window, you must first close the existing Firefox process, or restart your system."
I was not able to reproduce the reported behavior that the default profile would sometimes open a new window in the wrong profile. I launched it at least 10 times, and I got the "already running" dialog box every time.
Sorry, that wasn't tested with an official build. Tested again with Mozilla/5.0 (X11; U; Linux i686; en-US; rv:126.96.36.199) Gecko/2007051502 Firefox/188.8.131.52. The results are more in line with the report now.
If there are no Fx windows open, then "-P <profile>" does what you'd expect.
If there is an existing Fx process open with profile A, all subsequent executions of "firefox -P <profile>" will open a new window using profile A, regardless of the profile specified by <profile>. So, if I started with default and then tried profile A and then profile B, there would be three windows open with the default profile. If I started with profile A and then tried profile B and then the default profile, there would be three windows open with profile A.
Using this build, I never saw the message about an unresponsive Fx process that I previously reported.
A work-around is to use --no-remote. "firefox -P <profile> --no-remote" did what I expected every time.
Reporter, can you confirm that you get the expected results if you use --no-remote?
Me, I have two profiles here, running Firefox 184.108.40.206 on a Linux box (Ubuntu Gutsy). One is the default profile, one is called Java. The Java profile button also gives the --no-remote argument.
The following happens:
- When no firefox is running, the chosen profile is loaded when I start Firefox. As expected.
- When I only have the default profile running:
- firefox -P default opens a new window with the default profile. Perfect.
- firefox -P Java opens a new window with the Java profile. Fine.
- When I only have the Java profile open:
- firefox -P Java opens a new window with the Java profile. Also fine.
- firefox with any arguments ("-ProfileManager" or "-P default") opens a new window with the Java profile. This is not what I expect.
the problem with -no-remote is that if there is already an instance open with that profile, firefox will refuse to open the new url
I can confirm the above, namely,
1. Firefox -P someprofile opens a new window in the current profile running in another Firefox window, not someprofile
2. Firefox -P someprofile --no-remote opens a new window in the right profile, but if one already is open for that profile, then the "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 is shown.
And I agree both are very counterintuitive. I'll work on a patch.
As noted in at least one other bug, I will not accept a patch for this; it increases the complexity of the remoting feature somewhat significantly for little benefit.