199

After launching the X11 app (XQuartz 2.3.6, xorg-server 1.4.2-apple56) on my Mac (OS X 10.6.8), opening an terminal in X11 and running xhost +, I then ssh -Y to my Ubuntu 10.04 VM (running on VMware Fusion). When I run gedit .bashrc (for example), I get:

(gedit:9510): Gtk-WARNING **: cannot open display:

set | grep DISPLAY returns nothing.

But if I ssh -Y into my Ubuntu 11.04 machine, gedit .bashrc works. echo $DISPLAY returns "localhost:10.0".

I tried export DISPLAY=localhost:10.0 while sshed into my VM and then running gedit .bashrc, but I get:

(gedit:9625): Gtk-WARNING **: cannot open display: localhost:10.0

What could be different in the configuration of the two difference Ubuntu machines that would explain why one works and the other doesn't?

Update: As suggested by Zoredache in the comment below, I ran sudo apt-get install xbase-clients, but I continue to have the same problem.

Community
  • 1
Daryl Spitzer
  • 9,065

16 Answers16

102

From xhost+ : How to Fix “Cannot Open Display” Error While Launching GUI on Remote Server:

Answer: You can fix the “cannot open display” error by following the xhost procedure mentioned in this article.

Allow clients to connect from any host using xhost+

Execute the following command to disable the access control, by which you can allow clients to connect from any host.

$ xhost +

access control disabled, clients can connect from any host

Enable X11 forwarding

While doing ssh use the option -X to enable X11 forwarding.

$ ssh username@hostname -X

Enable trusted X11 forwarding, by using the -Y option,

$ ssh username@hostname -Y

Open GUI applications in that host

After opening ssh connection to the remote host as explained above, you can open any GUI application which will open it without any issue.

If you still get the “cannot open display” error, set the DISPLAY variable as shown below.

$ export DISPLAY='IP:0.0'

Note: IP is the local workstation’s IP where you want the GUI application to be displayed.

harrymc
  • 498,455
69

Check the server's sshd_config (normally /etc/ssh/sshd_config), and make sure X11Forwarding option is enabled with the line

X11Forwarding yes

If X11Forwarding is not specified, the default is no on the Debian machines I have available to check.

pevik
  • 600
DerfK
  • 1,259
  • 10
  • 13
30

I've had this problem when logging into a Ubuntu VM from Mac OS X as well -- it doesn't seem to like 'localhost' in the display variable for some reason. So set the IP manually, as harrymc suggests:

export DISPLAY="127.0.0.1:10.0"

Then X11 programs should be fine. It doesn't seem like it should be necessary to tell the OS that localhost and 127.0.0.1 are equivalent, but it works, at least.

SpinUp __ A Davis
  • 698
19

If you have this problem after some time when running with -X arg. or just ForwardX11 in /etc/ssh/ssh_config, then run $ ssh username@hostname -Y, to enable trusted X11 forwarding, don't know the exact cause but I'm guessing with -X some features expire after some time, probably to increase security.

Here is what I found online :

If you use ssh -X remotemachine the remote machine is treated as an untrusted client. So your local client sends a command to the remote machine and receives the graphical output. If your command violates some security settings you'll receive an error instead.

But if you use ssh -Y remotemachine the remote machine is treated as trusted client. This last option can open security problems. Because other graphical (X11) client could sniff data from the remote machine (make screenshots, do keylogging and other nasty stuff) and it is even possible to alter those data.

If you want to know more about those things I suggest reading the Xsecurity manpage or the X Security extension spec. Furthermore you can check the options ForwardX11 and ForwardX11Trusted in your /etc/ssh/ssh_config.

sources:

Community
  • 1
Stefan Rogin
  • 425
  • 4
  • 11
18

I had this problem with my CentOS KVM server, I was missing the "xauth" program.

Joril
  • 2,035
11

Just Tested On My Mac, Other Systems Might Be OK:

  1. Allow clients to connect from any host using xhost+

    $ xhost +

  2. You should have an environment that support X11 display

    [Mac System] Install X11 for mac https://www.xquartz.org/

  3. You should let your ssh-server forward x11 display

    update /etc/ssh/sshd_config and set X11Forwarding yes, then restart your ssh server

  4. You should let your ssh session forward x11 display with -X parameter

    $ ssh -X user@ip

  5. How to open X11 app in PyCharm?
    • open a ssh session that support X11 display(remember to keep this session)
    • run echo $DISPLAY in that ssh session
    • set DISPLAY environment variable for your PyCharm
Color
  • 211
10

I had to put in /etc/ssh/sshd_config the following:

X11UseLocalhost no

Rather then setting it "yes". Strange if the default is "NO" Users using putty with XMing under Windows. I use straight ssh over Fedora. Occasionally it would start giving us

error can't open display localhost

Reboot of the server would usually fix it but this is stupid. Did the above, restarted the service sshd on the server and presto new connections working fine again.

Scott - Слава Україні
  • 22,532
Luigi
  • 101
6

This setup works for me:

Local (64 bit Cygwin on Windows 10) DISPLAY=:0

Server (Amazon EC2 RHEL 7.6) DISPLAY=:10.0

These settings were found by clicking "X applications menu on :0" in taskbar and selecting System Tools > Terminal

qwr
  • 1,005
6

When running UXTERM or XTERM just issue 

export $DISPLAY

The variable will be there. Then just set it and export it.

slhck
  • 235,242
Oracle2066
  • 61
3

I also had this problem with Solaris 10 and found that the listener was not set up.

svccfg –s /application/x11/x11-server listprop options/tcp_listen
svccfg –s /application/x11/x11-server setprop  options/tcp_listen = true
G-Man Says 'Reinstate Monica'
  • 8,029
Doug Somers
  • 31
2

open terminal $ ssh username@hostname -X 

$ ssh username@hostname -Y

$ export DISPLAY='IP:0.0'

export DISPLAY="127.0.0.1:10.0" all should work.

Kenny Gichuhi
  • 21
1

I just found a nice hiccup in my setup that prevented x forwarding: My firewall was blocking all connections from localhost, thus preventing the tunnel to be reached

Pelle
  • 306
1

If you happen to be using Konsole simply switch to another terminal emulator such as Xfce Terminal and try again using root.

oliver
  • 111
1

I ran into this problem often and finally I figured out the issue and resolved it. Here is the checklist.

Make sure all the following conditions are satisfied.

  • X11Forwarding yes (check in /etc/ssh/sshd_config)

  • ssh -Y username@remoteserver.de(important: -Y)

If you have to make multiple hops to reach your destination server, make sure to use ssh -Y ... at all ssh connections. This is one of the reasons display failed for me because I simply used ssh username@remote_host.de at one of the connections.

pevik
  • 600
kmario23
  • 183
1

On CentOS 6.5, I suddenly lost remote X-programs access after messing with /etc/hosts. Same symptom of empty $DISPLAY variable (no help setting/exporting it manually).

The 127.0.0.1 entry pointing to the actual hostname is necessary; in fact the order seems to be also relevant (put last & it won't work...)

[root@poseidon /etc]$ cat hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1       localhost.localdomain localhost
::1     localhost6.localdomain6 localhost6
127.0.0.1 poseidon.mycampus.edu poseidon
1XX.XXX.XXX.208 poseidon.mycampus.edu poseidon

After fixing this, xeyes, xclock and other X test toys are working again, therefore my needed virt-manager is also back on line.

David Ramirez
  • 141
0

Something else to check is if you are in an elevated prompt or are using another user's bash.

If you have run sudo su and try to open an X11 window, that won't work until you revert back to your original ssh bash.

Gabriel Fair
  • 4,093