On Tue, Jul 11, 2006 at 01:43:04AM -0400, Eric Dorland wrote: > > That's never going to trigger. When the argument was received it was stored > > in prev, and later it was processed from prev. It will never reach the > > elif. > > Ok, well that problem should be fixed in the latest upload.
Yes, looks good now. > Hmm, could you try repeating these experiments with --verbose and > sending the results? Sure. > > Fixing that won't fix the underlying bug, though, since the MOZ_NO_REMOTE > > workaround does not appear to work. I just tried it; maybe I'm > > misunderstanding. I've got a single firefox running using the default > > profile and application ID during all these tests. > > > > % firefox -P hacking -a other > > > > -> Starts a new firefox process, does not return until that is closed. > > -> I close it. Good so far. % firefox --verbose -P hacking -a other FIREFOX_DSP= APPLICATION_ID=other CMDLINE_DISPLAY= DISPLAY=:0.0 OPTIONS=-P hacking -a other DEBUG=0 DEBUGGER= MOZ_DISABLE_PANGO= MOZ_NO_REMOTE=1 Running: /usr/lib/firefox/firefox-bin -P hacking -a other Same results. > > % firefox -a other > > > > -> Error dialog. I've gathered that this is expected, but the > > -> error message doesn't explain what's going on and neither does > > -> the man page. I close the dialog. % firefox --verbose -a other FIREFOX_DSP= APPLICATION_ID=other CMDLINE_DISPLAY= DISPLAY=:0.0 OPTIONS=-a other DEBUG=0 DEBUGGER= MOZ_DISABLE_PANGO= MOZ_NO_REMOTE= Running: /usr/lib/firefox/firefox-bin -a other Same results. The dialog box still 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." > > % firefox -P hacking -a firefox > > > > -> Firefox opens a new window in the default profile, ignoring -P. > > -> NOTE: This seems wrong. > > -> I close it. % firefox --verbose -P hacking -a firefox FIREFOX_DSP= APPLICATION_ID=firefox CMDLINE_DISPLAY= DISPLAY=:0.0 OPTIONS=-P hacking -a firefox DEBUG=0 DEBUGGER= MOZ_DISABLE_PANGO= MOZ_NO_REMOTE=1 Running: /usr/lib/firefox/firefox-bin -P hacking -a firefox I get a new window in the 'hacking' profile. -P is not ignored. This is confusing to me; I would have expected that the already running firefox (which has options -P default -a firefox) would have objected to this. But we've disabled remote operation so I guess we never asked it :-) > > % firefox -P hacking -a firefox -no-remote > > > > -> Firefox opens a new window in the alternate profile. I now have > > -> two running with the same agent ID, presumably firefox does not > > -> check at startup with MOZ_NO_REMOTE. A little strange. I close it. Behaves exactly as -P hacking -a firefox now. > > % firefox -P hacking -a other > > > > -> Firefox opens a new binary in the alternate profile automatically. > > -> Good. I move it to the background (do not close it). % firefox --verbose -P hacking -a other FIREFOX_DSP= APPLICATION_ID=other CMDLINE_DISPLAY= DISPLAY=:0.0 OPTIONS=-P hacking -a other DEBUG=0 DEBUGGER= MOZ_DISABLE_PANGO= MOZ_NO_REMOTE=1 Running: /usr/lib/firefox/firefox-bin -P hacking -a other Sam results. > > % firefox -P hacking -a other > > > > -> Error dialog. It has failed to communicate with either of the > > -> running firefox sessions. I can't tell if this is expected > > -> or not. % firefox --verbose -P hacking -a other FIREFOX_DSP= APPLICATION_ID=other CMDLINE_DISPLAY= DISPLAY=:0.0 OPTIONS=-P hacking -a other DEBUG=0 DEBUGGER= MOZ_DISABLE_PANGO= MOZ_NO_REMOTE=1 Running: /usr/lib/firefox/firefox-bin -P hacking -a other Same error dialog. > > % firefox -P hacking -a other -no-remote > > > > -> Error dialog again. Huh? Same one, could not communicate > > -> with the remote process, not something sensible like "profile in use". > > -> Changing the application ID has no effect. Same as without -no-remote, of course. > > So, I can now run up to a single firefox window per profile for alternate > > profiles, which is better than nothing, but not by a lot. By default firefox uses the profile from profiles.ini. I used to have some trouble with it changing the default unexpectedly, so my GNOME toolbar button for firefox says "firefox -P default". Now that the implicit -no-remote behavior has been fixed, this generates the same dialog box as several of the cases above. Try it: firefox & sleep 2 # So it pops up a window firefox -P default -> error dialog All I want is to be able to have two running firefox sessions, in different profiles, and two buttons on my toolbar to pop up a new windows, one for each profile. Using just -a doesn't work either: firefox & firefox -P hacking -a other & firefox -a firefox # Works! firefox -P hacking -a other # Error box firefox -a other # Error box -- Daniel Jacobowitz CodeSourcery -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
