Error Cant Open Display
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings error can't open display xming and policies of this site About Us Learn more about Stack Overflow the
Xterm Xt Error Can't Open Display
company Business Learn more about hiring developers or posting ads with us Unix & Linux Questions Tags Users Badges error can't open display localhost 10.0 putty Unanswered Ask Question _ Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a
Error Can't Open Display 0
minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top X client forwarded over SSH “cannot open display: localhost:11.0” up vote 13 down vote favorite 2 I have enabled X forwarding on remote machine where SSH server is running: # grep -i forward /etc/ssh/sshd_config X11Forwarding yes error can't open display cygwin # On local machine, I have started SSH client with -X flag which instructs the SSH server, running on remote machine, to set up a X-server proxy. In addition, it creates the $DISPLAY variable which points to this proxy and calls the xauth to install a proxy key which authenticates to this X-server proxy on remote machine: # echo "$DISPLAY" localhost:11.0 # xauth list | grep 11 A58/unix:11 MIT-MAGIC-COOKIE-1 39324086672d1ae35e373476c3891a77 # However, X clients on remote machine do not start properly: # wireshark (wireshark:10083): Gtk-WARNING **: cannot open display: localhost:11.0 # xterm Warning: This program is an suid-root program or is being run by the root user. The full text of the error or warning message cannot be safely formatted in this environment. You may get a more descriptive message by running the program as a non-root user or by removing the suid bit on the executable. xterm: Xt error: Can't open display: %s # X forwarding doesn't use xhost so at least this can be excluded. I tried to find some useful log entries both on machine where SSH server is running and machine where
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta
Error Can't Open Display Localhost
Discuss the workings and policies of this site About Us Learn more
Error Can't Open Display (null)
about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Super error can't open display (null) failed creating new xdo instance User Questions Tags Users Badges Unanswered Ask Question _ Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a http://unix.stackexchange.com/questions/108679/x-client-forwarded-over-ssh-cannot-open-display-localhost11-0/109322 minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top How do I fix a “cannot open display” error when opening an X program after ssh'ing with X11 forwarding enabled? up vote 50 down vote favorite 22 After launching the X11 app http://superuser.com/questions/310197/how-do-i-fix-a-cannot-open-display-error-when-opening-an-x-program-after-sshi (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. ssh display xorg gtk share|improve this question edited Feb 9 '14 at 12:20 Pablo Saratxaga 1133 asked Jul 13 '11 at 18:13 Daryl Spitzer 2,91893236 migrated from serverfault.com Jul 13 '11 at 18:31
Haritası Araçlar Sayfa Bağlantıları İlğili Değişiklikler Özel Sayfalar Sponsors Diğer Diller Deutsch SDBtartışmaKaynağı görgeçmiş SDB:X Client Produces "Can't open display" Error tagline: openSUSE sitesinden Konu başlıkları 1 Symptom 2 Background 3 Possible cause #1: no valid X authentication https://tr.opensuse.org/SDB:X_Client_Produces_%22Can't_open_display%22_Error credentials 4 Solution to the authentication credentials problem: sux 5 Possible cause #2: the X server isn't listening 6 Solution for local connections 7 Preferred solution for non-local X connections: ssh 8 Alternative solution for non-local X connections: enable TCP/IP socket connections 9 More information on running X applications remotely Symptom Under SUSE Linux Enterprise Server 9 or a related version of SUSE Linux, an X client application, for open display example xterm, reports an error Can't open display on startup, for instance xterm Xt error: Can't open display: localhost:0.0. Background The X Window System is a network transparent window system that uses a client/server-architecture. X can use a number of transport protocols, including Unix sockets (which are an inter-process communication facility that is local to a system) and TCP/IP sockets (connections using the Internet protocol s uite). Which mechanism error can't open is used, is determined by the format of the DISPLAY environment variable. When DISPLAY does not contain a hostname, e.g. it is set to :0, Unix sockets will be used. When it does contain a hostname, e.g. it is set to localhost:0.0, the X client application will try to connect to the server (in the example, localhost) via TCP/IP sockets rather than via Unix sockets. X has its own authentication mechanism to determine whether a client is allowed to connect to a server; this is used, for example, to prevent another user from being able to view or manipulate your X session. As the Internet has become an increasingly hostile environment, it has become good practice to only open up services to the Internet when they are really needed. Possible cause #1: no valid X authentication credentials With the default X authentication mechanism, an X client needs to have access to a valid X session cookie (which is, essentially, a shared secret between the X server and its clients). When a user switches to a different user using the su command, X session cookies are not transferred and thus the user cannot start X applications under the user id to which he or she switch