Simpler Navigation for Servers and Operating Systems - Please Update Your Bookmarks
Completed: a much simpler Servers and Operating Systems section of the Community. We combined many of the older boards, so you won't have to click through so many levels to get at the information you need. Check the consolidated boards here as many sub-forums are now single boards.
If you have bookmarked forums or discussion boards in Servers and Operating Systems, we suggest you check and update them as needed.
Showing results for 
Search instead for 
Did you mean: 

Problem running remote X applications on a Mac OS X 10.5.5 Intel system

Andrew Kaplan
Super Advisor

Problem running remote X applications on a Mac OS X 10.5.5 Intel system

Hi there --

One of our users is trying to connect to a remote Linux system from his Mac, and then run several X applications on that system. He opens up an X terminal, and first types in the following command:

xhost +

He then connects via ssh to the remote system using the following command syntax:

ssh -X -l

Once he is on the remote system, his command shell is tcsh, and the following command is entered:

setenv DISPLAY :0.0

When he tries to start xemacs, or any X application for that matter, he gets the following error message:

X server not responding

Several other users have used the above procedure, and have been able to start the remote X applications without a problem.

Has anyone seen this, and know what the fix is to this problem? Thanks.
A Journey In The Quest Of Knowledge
Steven Schweda
Honored Contributor

Re: Problem running remote X applications on a Mac OS X 10.5.5 Intel system

I don't normally deal with it, but ...

> [...] a remote Linux system [...]

How "remote"? (How many X-blocking firewalls
in between?)

I thought that "ssh -X" was supposed to deal
with all the DISPLAY stuff by itself. What
happens if you leave out this step?:

setenv DISPLAY :0.0

Around here (Mac OS 10.4.11), "man ssh" says:

The user should not manually set DISPLAY.
Forwarding of X11 connections can be
configured on the command line or in
configuration files.

Doing it yourself bypasses the X forwarding
stuff in SSH. You can do that, but it does
make the "-X" rather pointless, and it also
means that you need to get at port 6000 on
the Mac instead of just the SSH stuff.

There's also sshd configuration on the server
side to worry about (about which I also know