SEO

/dev/rob0 wrote:
> In article <3F208361.1050303@spamerssuck.earthlink.net>, Tom wrote:
>
>>well. I am able to get xeyes to start from one box to the other
>>remotely about 3 times out of 10 and I can't get anything else, such as
>>galeon or mozilla, to run remotely at all... anyone know what the
>>problem could be?
>
>
> Yes. 70% of the time you run xeyes, and 100% of the time you run galeon
> or mozilla, you are doing something wrong.
>
> The easiest way to do remote X is to change your /etc/ssh/sshd_config to
> include this line:
> X11Forwarding yes
> Then "/etc/rc.d/rc.sshd restart" and add the -X to your ssh command
> line. When you thus connect from an X terminal you can easily run X apps
> on the remote machine.
>
> The easiest way to get good information is to tell us WHAT YOU DID when
> something didn't work as you expected. Not all of us here are mind
> readers.

I'm not doing anything differently at all though... I've never seen
this sort of thing happen before. I used to run reflection x on windows
with my previous version of slack and no issues at all... I did ad the
line to /etc/ssh/sshd_config and issued the restart command, but I get
the same results... which gives me an idea. I'll try to see if I can
get it to work by booting into Windows and seeing what happens.

I've also tried plain telnet with the same results though...

On Fri, 25 Jul 2003 03:09:55 GMT, Tom <tommyinla@spamerssuck.earthlink.net>
wrote:
> I'm not doing anything differently at all though... I've never seen
> this sort of thing happen before. I used to run reflection x on windows
> with my previous version of slack and no issues at all...

Right now, are you trying to get the X display on a Windows machine,
Linux machine, or something else?

> I did ad the
> line to /etc/ssh/sshd_config and issued the restart command, but I get
> the same results...

That will only affect X11 Forwarding over SSH and won't affect telnet
at all. Are you trying to use X Forwarding over SSH or plain X11 over
TCP?

If the latter, is there a firewall on the machine running the X server
(i.e the one you want the application display on) and is the X server
listening for TCP connections?

What is $DISPLAY set to in your shell?


--
Simon <simon@no-dns-yet.org.uk> **** GPG: F4A23C69
"We demand rigidly defined areas of doubt and uncertainty."
- Douglas Adams

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Tom <tommyinla@spamerssuck.earthlink.net> is thought to have
typed the following text on Fri, 25 Jul 2003 at 03:09 GMT:

> I'm not doing anything differently at all though... I've never seen

That really doesn't give us any clues, please describe *every* command
you issue from login to failure of the app. Maybe someone will spot an
error.

- --
Bartosz Oudekerk

Wizard guild parking ONLY! Violators will be toad.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE/IOU4256ZyNYAOpkRAj5CAJ97Qy0GjXNiHumbRYiTJaQmWaDYuw CghMq7
IIueMoiGTINR+qoiVq98oDc=
=WkI0
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In article <3F220169.7080304@spamerssuck.earthlink.net>, Tom wrote:

> I'm trying from Linux machine to Linux machine. Both have the exact
> same distro (Slack 8.1) with the same kernel and both have all software
> installed from the install.
>
> X runs fine on both machines.
>
> I've tried both ssh and telnet.

Don't use telnet. (Unless your boss makes you.)

> Here's what I do from my machine (pitt is the remote host, apollo is the
> local host):
>
> $ ssh pitt

It should default to -X, but you can use it to make sure. If
tunnelling doesn't work, using -X will allow you to be alerted.

> $ export DISPLAY=apollo:0.0

Don't do this. ssh sets up the X11Forwarding for you. If you
type set after ssh'ing in from apollo to pitt, you should see a
DISPLAY variable set (something like localhost:10.0).

> I get xeyes to work about 3 times out of 10. Nothing major (eg. galeon,
> mozilla, etc.) will work...

Well, with ssh that's 3 times out of 10 it *shouldn't* work.

Yes, there are ways of making X11 work with telnet, or without
ssh X11 forwarding, but as you've discovered it's a pain. Just
stick with ssh doing the X11 for you, and it'll Just Work between
pretty much any two hosts without having to diddle with $DISPLAY.

- --keith

- --
kkeller-mmmspam@wombat.san-francisco.ca.us
(try just my userid to email me)
alt.os.linux.slackware FAQ: http://wombat.san-francisco.ca.us/cgi-bin/fom

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iEYEARECAAYFAj8iySgACgkQhVcNCxZ5ID+lagCgg+NtLPWKUH LMj6NN/NVxJZwX
jokAniHYh1+k74er3N7BwJtS9oMAqsYm
=2UsZ
-----END PGP SIGNATURE-----

>>I've tried both ssh and telnet.
>
>
> Don't use telnet. (Unless your boss makes you.)
>

I was only testing with telnet to see what would happen. Telnet isn't
running on that box.

>>
>>$ ssh pitt
>
>
> It should default to -X, but you can use it to make sure. If
> tunnelling doesn't work, using -X will allow you to be alerted.
>

ssh -X fixed works!!! It works flawlessly every single time... thank
you!!!

>
>>$ export DISPLAY=apollo:0.0
>
>
> Don't do this. ssh sets up the X11Forwarding for you. If you
> type set after ssh'ing in from apollo to pitt, you should see a
> DISPLAY variable set (something like localhost:10.0).
>


Thanks again

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In article <3F2303FC.2060707@spamerssuck.earthlink.net>, Tom wrote:
>
> ssh -X fixed works!!! It works flawlessly every single time... thank
> you!!!

I believe there's a config file where you can make -X the default.
Check the ssh man page for details.

- --keith

- --
kkeller-mmmspam@wombat.san-francisco.ca.us
(try just my userid to email me)
alt.os.linux.slackware FAQ: http://wombat.san-francisco.ca.us/cgi-bin/fom

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iEYEARECAAYFAj8kUFoACgkQhVcNCxZ5ID8laACfS55JaevVyM SLbOyFmeEojED1
recAniwj57IFm7qkm3qREbFW7GJ5+BfB
=dQFA
-----END PGP SIGNATURE-----