This is causing me a serious headache, in that I'm now no longer able to open links remotely.
Here's my use case. I'm logged in to my laptop, machineA (running linux with X11). However, I read email with emacs rmail on my server, machineB (the emacs is running on machineB, connecting to the display on machineA -- I ssh login to machineB).
The solutions proposed here would appear to create a new firefox running on machineB. That's not what I want. Aside from the performance penalty, it means that when I move machineA around (take it to work, or whatever), the firefox in question would go away.
I don't care about the -ping option. I start firefox on login, so it's always around; if for some reason it goes away, I just restart it.
The upshot is that there now appears to be no way to do this. I'm not willing to switch mailers or anything like that. I guess I'll have to back off to firefox 35 until this capability is restored.
This is causing me a serious headache, in that I'm now no longer able to open links remotely.
Here's my use case. I'm logged in to my laptop, machineA (running linux with X11). However, I read email with emacs rmail on my server, machineB (the emacs is running on machineB, connecting to the display on machineA -- I ssh login to machineB).
The solutions proposed here would appear to create a new firefox running on machineB. That's not what I want. Aside from the performance penalty, it means that when I move machineA around (take it to work, or whatever), the firefox in question would go away.
I don't care about the -ping option. I start firefox on login, so it's always around; if for some reason it goes away, I just restart it.
The upshot is that there now appears to be no way to do this. I'm not willing to switch mailers or anything like that. I guess I'll have to back off to firefox 35 until this capability is restored.