Hi Daniel,

* Daniel Jacobowitz ([EMAIL PROTECTED]) wrote:
> Package: firefox
> Version: 1.5.dfsg+1.5.0.3-2
> Severity: normal
> 
> This is related to the fix for bug #344849.
> 
> First:
> 
>     case "${arg}" in
>         .... -P | -CreateProfile)
>             prev=${arg}
>             continue
>         ;;
>     esac
> 
> Then:
> 
>     if [ "${prev}" ]; then
>         case "${prev}" in
>             -P|-CreateProfile)
>                 case "${arg}" in
>                 default)    APPLICATION_ID=firefox ;;
>                 *)          APPLICATION_ID=firefox--"${arg}" ;;
>                 esac
>                 set "$@" "${prev}" "${arg}"
>                 ;;
> 
> Then:
> 
>     elif [ "${arg}" ]; then
>         case "$arg" in
>             -P | -CreateProfile | -no-remote)
>                 MOZ_NO_REMOTE=1
>                 export MOZ_NO_REMOTE
>  
> 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. 
 
> 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 -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 -P hacking -a firefox
> 
> -> Firefox opens a new window in the default profile, ignoring -P.
> -> NOTE: This seems wrong.
> -> I close 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.
> 
> % 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 -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 -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.
> 
> 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.

Hmm, could you try repeating these experiments with --verbose and
sending the results? 

-- 
Eric Dorland <[EMAIL PROTECTED]>
ICQ: #61138586, Jabber: [EMAIL PROTECTED]
1024D/16D970C6 097C 4861 9934 27A0 8E1C  2B0A 61E9 8ECF 16D9 70C6

Attachment: signature.asc
Description: Digital signature

Reply via email to