[opensuse] Remote Firefox via ssh
When I was recently using http://software.opensuse.org/search to install some packages on my firewall, I used Firefox, installed on the firewall, to access that site. However, one thing I noticed is that when I start Firefox with ssh from an account that's also on the local computer, the local copy of Firefox starts up, instead of the one on the firewall. However, if I use a different account, including root, Firefox on the firewall runs as intended. I had previously noticed the same behaviour when attempting to run Seamonkey, on my main computer, remotely from my notebook. Generally, when running an X app remotely, the app on the remote computer starts. Why the difference with Seamonkey & Firefox? All computers involved are running some version of OpenSUSE (11.0 or 11.3). -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Am 10.12.2010 17:40, schrieb James Knott:
When I was recently using http://software.opensuse.org/search to install some packages on my firewall, I used Firefox, installed on the firewall, to access that site. However, one thing I noticed is that when I start Firefox with ssh from an account that's also on the local computer, the local copy of Firefox starts up, instead of the one on the firewall. However, if I use a different account, including root, Firefox on the firewall runs as intended. I had previously noticed the same behaviour when attempting to run Seamonkey, on my main computer, remotely from my notebook. Generally, when running an X app remotely, the app on the remote computer starts. Why the difference with Seamonkey & Firefox? All computers involved are running some version of OpenSUSE (11.0 or 11.3).
Are you sure that the local Firefox/seamonkey starts up or is it already running? The latter is somehow normal as mozilla apps do something to avoid running multiple instances. This is done using some X methods. What always should work to avoid it is using -no-remote as commandline parameter. Wolfgang -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Wolfgang Rosenauer wrote:
Am 10.12.2010 17:40, schrieb James Knott:
When I was recently using http://software.opensuse.org/search to install some packages on my firewall, I used Firefox, installed on the firewall, to access that site. However, one thing I noticed is that when I start Firefox with ssh from an account that's also on the local computer, the local copy of Firefox starts up, instead of the one on the firewall. However, if I use a different account, including root, Firefox on the firewall runs as intended. I had previously noticed the same behaviour when attempting to run Seamonkey, on my main computer, remotely from my notebook. Generally, when running an X app remotely, the app on the remote computer starts. Why the difference with Seamonkey & Firefox? All computers involved are running some version of OpenSUSE (11.0 or 11.3).
Are you sure that the local Firefox/seamonkey starts up or is it already running? The latter is somehow normal as mozilla apps do something to avoid running multiple instances. This is done using some X methods. What always should work to avoid it is using -no-remote as commandline parameter.
I can confirm what Wolfgang says. And where the executable runs also determines which profile is used, which can lead to some 'interesting' side effects. I wish mozilla came with an option to disable all this unwanted cleverness. I'd just like it to behave like any other X application. Cheers, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Wolfgang Rosenauer wrote:
Are you sure that the local Firefox/seamonkey starts up or is it already running? The latter is somehow normal as mozilla apps do something to avoid running multiple instances. This is done using some X methods. What always should work to avoid it is using -no-remote as commandline parameter.
Yes, I usually have Firefox and/or Seamonkey running. However, why should an app on a remote computer open the same browser on the local computer? I'm running that app remotely, because I want to do something on that remote computer. In this instance, it is to install software on that remote computer. If this is some genius's idea of a "feature", I'd like to know how to turn it off, as it's worse than useless. BTW, this is a fairly recent thing, as it didn't work that way a few years ago. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
James Knott wrote:
Wolfgang Rosenauer wrote:
What always should work to avoid it is using -no-remote as commandline parameter.
I'd like to know how to turn it off
I think you missed this bit of what Wolfgang said Cheers, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Dave Howorth wrote:
I think you missed this bit of what Wolfgang said
That works. I guess I'll have to create an alias to fix this "feature". I really fail to understand the reasoning behind it. If I want to run a local copy, why would I go through all the trouble of logging into another computer, when I could just click on the icon??? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hi, Am 10.12.2010 18:02, schrieb James Knott:
Yes, I usually have Firefox and/or Seamonkey running. However, why should an app on a remote computer open the same browser on the local computer? I'm running that app remotely, because I want to do something on that remote computer. In this instance, it is to install software on that remote computer. If this is some genius's idea of a "feature", I'd like to know how to turn it off, as it's worse than useless. BTW, this is a fairly recent thing, as it didn't work that way a few years ago.
This feature is soooo old. It actually got ported from Netscape 4 to Mozilla many years ago. I think the reasoning was completely different. http://www.mozilla.org/unix/remote.html That it misbehaves for non local sessions is a side effect and caused by X's network transparency (again I guess). Wolfgang -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Wolfgang Rosenauer wrote:
That it misbehaves for non local sessions is a side effect and caused by X's network transparency (again I guess).
I used to frequently run Seamonkey remotely, a few years ago, and it didn't work that way then. When I start an app, any app remotely, I would expect it to run on the computer I started it on and nowhere else. That's the way every other app I've used works. I can certainly understand the usefulness of that remote command to start a remote session, but it shouldn't be force to come back in the other direction. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 12/10/2010 10:37 AM, James Knott wrote:
Wolfgang Rosenauer wrote:
That it misbehaves for non local sessions is a side effect and caused by X's network transparency (again I guess).
I used to frequently run Seamonkey remotely, a few years ago, and it didn't work that way then. When I start an app, any app remotely, I would expect it to run on the computer I started it on and nowhere else. That's the way every other app I've used works. I can certainly understand the usefulness of that remote command to start a remote session, but it shouldn't be force to come back in the other direction.
This just seems wrong on so many levels. That a remote session could even know that there was a local session running is a bit of a worry. -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (4)
-
Dave Howorth -
James Knott -
John Andersen -
Wolfgang Rosenauer