From: Aaron W. Hsu on
On Wed, 10 Feb 2010 02:17:17 -0500, Henrik Carlqvist
<Henrik.Carlqvist(a)deadspam.com> wrote:

> Even though I get an error about the display from my ssh session I am not
> able to get the error about display localhost:10.

What about doing something like this?

ssh -X host

which takes you into a shell. Then, print the environment for us. That
might reveal something. Also, try to run xclock once you are inside the
shell. I don't know why this would make a difference, but maybe we can get
more information.

Aaron W. Hsu

--
A professor is one who talks in someone else's sleep.
From: Mike Jones on
Responding to Aaron W. Hsu:

> On Wed, 10 Feb 2010 02:17:17 -0500, Henrik Carlqvist
> <Henrik.Carlqvist(a)deadspam.com> wrote:
>
>> Even though I get an error about the display from my ssh session I am
>> not able to get the error about display localhost:10.
>
> What about doing something like this?
>
> ssh -X host
>
> which takes you into a shell. Then, print the environment for us. That
> might reveal something. Also, try to run xclock once you are inside the
> shell. I don't know why this would make a difference, but maybe we can
> get more information.
>
> Aaron W. Hsu



I get

Error: Can't open display "localhost:10.0"

--
*=( http://www.thedailymash.co.uk/
*=( For all your UK news needs.
From: Joost Kremers on
Mike Jones wrote:
> Responding to Aaron W. Hsu:
>> What about doing something like this?
>>
>> ssh -X host
>
> I get
>
> Error: Can't open display "localhost:10.0"

you know, perhaps i'm just stupid and i don't understand this X-forwarding thing
at all, but from the logs you posted, i gather that this error message is *not*
from ssh (as it wasn't prepended with "debug0:" or something similar). so,
assuming it's an error from the X client (i.e., the X program running on the
remote machine), isn't it strange that it is trying to connect to localhost?
shouldn't that be 192.168.x.x (or 10.x.x.x, whichever you're using)?

i mean, to the X client localhost is the remote machine, while the display is on
the machine you're connecting from, where the X server is running. right?


--
Joost Kremers joostkremers(a)yahoo.com
Selbst in die Unterwelt dringt durch Spalten Licht
EN:SiS(9)
From: Bit Twister on
On 10 Feb 2010 11:02:49 GMT, Joost Kremers wrote:

> you know, perhaps i'm just stupid and i don't understand this
> X-forwarding thing at all, but from the logs you posted, i gather
> that this error message is *not* from ssh (as it wasn't prepended
> with "debug0:" or something similar). so, assuming it's an error
> from the X client (i.e., the X program running on the remote
> machine), isn't it strange that it is trying to connect to
> localhost?

Not in my setup.
Guessing actual IP comes from the SSH_CONNECTION variable built from
the SSH_CLIENT contents.

> i mean, to the X client localhost is the remote machine, while the
> display is on the machine you're connecting from, where the X server
> is running. right?

$ get_wan_ip.pl
71.170.056.46

$ echo $DISPLAY
:0.0

ssh $USER(a)kitty
$ get_wan_ip.pl
24.117.051.251

$ echo $DISPLAY
DISPLAY=localhost:10.0

$ env | grep 170.056
SSH_CLIENT=71.170.056.46 44543 22
SSH_CONNECTION=71.170.056.46 44543 24.117.051.251 22

From: Mike Jones on
Responding to Bit Twister:

[...]
>> i mean, to the X client localhost is the remote machine, while the
>> display is on the machine you're connecting from, where the X server is
>> running. right?
>
> $ get_wan_ip.pl
> 71.170.056.46
>
> $ echo $DISPLAY
> :0.0
>
> ssh $USER(a)kitty
> $ get_wan_ip.pl
> 24.117.051.251
>
> $ echo $DISPLAY
> DISPLAY=localhost:10.0


Hmmm?

On the server box...
$SRVR echo $DISPLAY
:0.0
$

On the client box...
$CLIENT echo $DISPLAY
:0.0
$

On the client box...
$CLIENT ssh $SRVR
$SRVR echo $DISPLAY

$

I just got a blank line on the RXVT I sshed to the SRVR on.

This looks wrong.

--
*=( http://www.thedailymash.co.uk/
*=( For all your UK news needs.