[becca]

Logging into my linux box gives me the following error
Xlib: connection to ":0.0" refused by server
Xlib: Invalid MIT-MAGIC-COOKIE-1 key
Error: Can't open display: :0.0
I'm logging in with -X which I thought took care of the display and xauth problems.
Help or point me to a relavent site please.
I've searched and can't find any thing useful.
Mick

[Tritium]

logging into your linux box and then doing what gives that error? Where are you starting the program? Are you using a capital or lowercase X as an argument?

[rantweasel]

Originally posted by becca:
Logging into my linux box gives me the following error
Xlib: connection to ":0.0" refused by server
Xlib: Invalid MIT-MAGIC-COOKIE-1 key
Error: Can't open display: :0.0

Make sure that your DISPLAY variable is set before you ssh to the other computer. In the terminal, just "echo $DISPLAY". If it isn't set, set it to either "localhost:0.0" or "<whatever the fully qualified hostname is>:0.0" and then ssh.

mathias

[int69h]

If you're running ssh from Terminal.app, ssh -X from within an xterm should solve your problem. Everything is already setup that way.

[drmbb2]

Originally posted by becca:
Logging into my linux box gives me the following error
Xlib: connection to ":0.0" refused by server
Xlib: Invalid MIT-MAGIC-COOKIE-1 key
Error: Can't open display: :0.0
I'm logging in with -X which I thought took care of the display and xauth problems.
Help or point me to a relavent site please.
I've searched and can't find any thing useful.
Mick

From what app are you ssh'ing to the linux machine? Terminal is not Xwindow so it cannot interpret the forwarded display. Executing this command from an X11 (i.e. XFree86 via compile or FINK install, or Apple's X11 app) will, and does, work (provided your Linux machine is running a full X11 server, of course). Note, if you do this from, say, XDarwin (as I do, from a binary install via the XonX project), you do not need to set any other display variables, just open XDarwin, execute "ssh -X <login>" and you are set.

[int69h]

There's no need for the remote box to be running an Xserver.

[drmbb2]

Originally posted by int69h:
There's no need for the remote box to be running an Xserver.

Err, am I missing something (honestly)? If the remote application is an X application, running on the remote server, it seems to me that the remote box MUST be running a X SERVER, in order to forward the display to the local X client (which merely interprets the X display from the remote box).

That's the way I understand it, and have always used it.

[Graymalkin]

You're yet another victim of X11's retarded nomenclature. The X11 definitions of client and servers are bass ackwards. The X server is the program running on the machine you're sitting in front of, be it a full fledged workstation or just a terminal. The X server controls the hardware you are interfacing with. The X client is the aspect of the X11 system that programs talk to as well as X servers. The X client sits on a machine and tells the X server what to display. This nomenclature is confusing and ridiculous but because it was too widely used it was never changed.

[becca]

Strange you sould bring up terminal window. I was leaning that way, but I got it to work by putting "DISPLAY=:0.0" in my .bash_profile
that also lets me run x apps within the terminal app without using "open-x" command.

Mick

[BigMac2]

The X11 forwarding is working fine for me, I used this with my Laptop and xmms to play music on my G4. But some change in the /etc/sshd_config and ssh_config was needed.

[mmurray]

Originally posted by Graymalkin:
You're yet another victim of X11's retarded nomenclature. The X11 definitions of client and servers are bass ackwards. The X server is the program running on the machine you're sitting in front of, be it a full fledged workstation or just a terminal. The X server controls the hardware you are interfacing with. The X client is the aspect of the X11 system that programs talk to as well as X servers. The X client sits on a machine and tells the X server what to display. This nomenclature is confusing and ridiculous but because it was too widely used it was never changed.

While I agree with you I have seen others argue that this is the correct nomenclature. The application on the remote machine needs a window to display in. Its a client. Your machine serves up windows it can use. So your machine is a server.

I think its like going into a restaurant and the waiters are all standing around wondering what to do with the food. They are looking for plates you offer them up a plate and they put food on it. So you are serving and they are clients. :-)

Michael