Re: [gentoo-user] Re: OT: urlview+Firefox 9 not co-operating

[Florian Philipp]

Am 29.01.2012 03:36, schrieb Walter Dnes:
> On Sat, Jan 28, 2012 at 03:53:11PM -0600, ??Q?? wrote
>> On Sat, 28 Jan 2012 15:35:46 -0500
>> "Walter Dnes" <waltdnes@××××××××.org> wrote:
>>
>>> On Sat, Jan 28, 2012 at 11:08:12AM +0100, Florian Philipp wrote
>>>
>>>> Add --no-remote to firefox's parameters.
>>         ^^
>> -no-remote
>> ^
>
>   I did notice that, and tried it both ways.  No difference.
>
>> Do you get the same error if you try
>>
>> $ /usr/bin/firefox -P default -new-window "http://www.gentoo.org"
>>
>> without using urlview?
>
>   Yes and No!  I've solved the problem, but this is weird; really really
> weird.  Let me explain.  I use ICEWM window manager.  For the firefox
> launchbar command I have always used...
>
> /usr/bin/firefox -width 950 -height 1050 -P default -no-remote
>
> and manually opened new windows with {CTRL-N}.  Urlview was always able
> to lauch a new window.  But now if one firefox window is opened with
> "-no-remote", I can *NOT* programatically open any more new Firefox
> windows.  That includes urlview and your commandline example *EVEN IF I
> USE "-new-window" TO OPEN ADDITIONAL WINDOWS*.  Only the manual {CTRL-N}
> command works.
>
>   After some trial and error, I changed ICEWM's launchbar command to
>
> /usr/bin/firefox -width 950 -height 1050 -P default -new-window
>
> Now I can open new windows all over the place with Urlview and your
> commandline example.  Problem solved.  ***ALWAYS USE "new-window"***.
> Computers never cease to amaze me.  Can you pop open 2 xterms and try
> the following?  The first pair should work...
>
> in xterm 1 ==> /usr/bin/firefox -new-window "http://www.gentoo.org"
> in xterm 2 ==> /usr/bin/firefox -new-window "http://www.cnn.com"
>
>   Now close both Firefox windows and try...
>
> in xterm 1 ==> /usr/bin/firefox -no-remote "http://www.gentoo.org"
> in xterm 2 ==> /usr/bin/firefox -new-window "http://www.cnn.com"
>
>   The first firefox opens, but the second one fails.
>

It kind-of makes sense. -no-remote apparently does not only deactivate
the "attach-to-other-process" functionality but also the
"be-ready-that-others-attach-to-you" function. So the second firefox
tries to attach to the first but that doesn't react, therefore it panics.

Regards,
Florian Philipp