Error Cannot Open Display Localhost
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about error cannot open display localhost 10.0 putty hiring developers or posting ads with us Unix & Linux Questions Tags Users Badges Unanswered Ask can't open display localhost Question _ Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join unable to open display localhost them; it only takes a 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”
Error Can't Open Display Localhost 10.0 Putty
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 # 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 error can't open display linux 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 SSH client is running with find /var/log/ -mmin -5 -type f command, but this did not give any hints. SSH server version is OpenSSH_5.9p1 and SSH client version is OpenSSH_5.2p1. Output of /tmp/.X11-unix/ directory on remote machine can be seen below: # ls -la /tmp/.X11-unix/ total 0 drwxrwxrwt 2 root root 40 Dec 9 15:44 . drwxrwxrwt 4 root root 80 Jan 13 09:17 .. # As seen above, there are no Unix domain sockets there. Output of strace xterm is following: # strace xterm execve("/usr/bin/xterm", ["xterm"], [/* 16 vars */]) = 0 brk(0) = 0x9e50000 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory) m
Pages: 1 #1 2010-01-16 00:41:20 Greenstuff Member From: Israel Registered: 2009-06-30 Posts: 64 [Solved] Xforwarding with ssh: Can't open display localhost 10.0 Hey, I have the following trouble: I xhost unable to open display have a server with Xauth installed and forewarding enabled. However, I
Gtk Warning Cannot Open Display Ubuntu
seem to get the following massage after running ssh -X $host xclock:Error: Can't open display: localhost:10.0Here's my server's
Gtk Warning Cannot Open Display Gedit
/etc/ssh/sshd_config file:#Port 22ListenAddress 0.0.0.0#ListenAddress ::Protocol 2ChallengeResponseAuthentication noUsePAM yesXAuthLocation /usr/bin/xauthAllowAgentForwarding yesAllowTcpForwarding yesX11Forwarding yesX11DisplayOffset 10X11UseLocalhost yesSubsystem sftp /usr/lib/ssh/sftp-serverAny help is much appriciated!EDIT:Tried setting AllowX11Forwarding yes in the /etc/ssh/sshd2_config file, http://unix.stackexchange.com/questions/108679/x-client-forwarded-over-ssh-cannot-open-display-localhost11-0 but it didn't help Last edited by Greenstuff (2010-01-16 13:16:55) Offline #2 2010-01-16 03:22:25 pyther Member Registered: 2008-01-21 Posts: 1,395 Website Re: [Solved] Xforwarding with ssh: Can't open display localhost 10.0 I always had to do 'xhost +' w/out quotes on the client machine. Try that and see if that helps. Website - Blog - arch-homeArch User since March https://bbs.archlinux.org/viewtopic.php?id=88883 2005 Offline #3 2010-01-16 10:13:00 Greenstuff Member From: Israel Registered: 2009-06-30 Posts: 64 Re: [Solved] Xforwarding with ssh: Can't open display localhost 10.0 pyther wrote:I always had to do 'xhost +' w/out quotes on the client machine. Try that and see if that helps.Nope, problem persists Offline #4 2010-01-16 13:16:39 Greenstuff Member From: Israel Registered: 2009-06-30 Posts: 64 Re: [Solved] Xforwarding with ssh: Can't open display localhost 10.0 Ok, I talked to people at IRC. Finally one gave me the answer: I needed to put this in /etc/hosts:127.0.0.1 localhostThis fixed it for me. Offline Pages: 1 Index »Networking, Server, and Protection »[Solved] Xforwarding with ssh: Can't open display localhost 10.0 Board footer Jump to Newbie Corner Installation Kernel & Hardware Applications & Desktop Environments Laptop Issues Networking, Server, and Protection Multimedia and Games System Administration Other Architectures Announcements, Package & Security Advisories Arch Discussion Forum & Wiki discussion Pacman & Package Upgrade Issues [testing] Repo Forum Creating & Modifying Packages AUR Issues, Discussion & PKGBUILD Requests GNU/Linux Discussion Community Contributions Programming & Scripting Other Languages
- gedit - from SSH login Issues related to applications and software problems Post Reply Print view Search Advanced search 9 posts http://www.centos.org/forums/viewtopic.php?t=54325 • Page 1 of 1 Narain Posts: 4 Joined: 2015/09/24 16:51:59 Cannot open display - gedit - from SSH login Quote Postby Narain » 2015/09/24 17:04:19 Hi all,We have installed http://www.softpanorama.org/Xwindows/Troubleshooting/can_not_open_display.shtml the 7.1.1503_core version of CentOS. When logging in remotely through SSH (ssh -y narain@192.168.x.x), and typing in gedit, throws the following error:** (gedit:2290): WARNING **: Could not open X open display display(gedit:2290): Gtk-WARNING **: cannot open display: 192.168.x.x:17.0 //the x.x is intentionally replacedI have verified the installation of xorg-x11-xauth, and the server SSH config file /etc/ssh/sshd_config includes the following:#GatewayPorts noX11Forwarding yesX11DisplayOffset 10X11UseLocalhost yes#PermitTTY yesI have no clue on the next step to try to resolve this issue and would greatly appreciate your help! Many thanks! Top TrevorH Forum Moderator open display localhost Posts: 16773 Joined: 2009/09/24 10:40:56 Location: Brighton, UK Re: Cannot open display - gedit - from SSH login Quote Postby TrevorH » 2015/09/24 18:11:38 Do you have X running on the machine that you are ssh'ing from? Full time Geek, part time moderator. Use the FAQ Luke Top toracat Forum Moderator Posts: 7149 Joined: 2006/09/03 16:37:24 Location: California, US Contact: Contact toracat Website Re: Cannot open display - gedit - from SSH login Quote Postby toracat » 2015/09/24 18:40:14 Narain wrote:Hi all,We have installed the 7.1.1503_core version of CentOS. When logging in remotely through SSH (ssh -y narain@192.168.x.x), and typing in gedit, throws the following error:It's supposed to be ssh -Y (or ssh -X). Note the uppercase letter. CentOS Forum FAQ Top TrevorH Forum Moderator Posts: 16773 Joined: 2009/09/24 10:40:56 Location: Brighton, UK Re: Cannot open display - gedit - from SSH login Quote Postby TrevorH » 2015/09/24 23:15:54 Also, ssh X11 forwarding DISPLAY variables are invariably of the format localhost:10.0 (the numbers may vary) and do not use ip addresses. Are you attemptin
Architecture X display manager Reinstallation of X11 and Gnome Desktop in RHEL "init: Id "x" respawning too fast: disabled for 5 minutes." Configuration Fonts in X Exporting_display Xdefaults Using xauth Too high refresh rate ot too high resolution XDMCP vnc Cygwin/X X11 security Tips History Humor Etc The X Window uses a client/server-architecture (and the server is your workstation to which you are exporting the session). It can use a number of transport protocols, including Unix sockets and TCP/IP sockets. Which mechanism 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 (even localhost as in the example) via TCP/IP sockets X has an authentication mechanism, which decides whether a client is allowed to connect to a server. 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. Recently in some Linux distributions, X is by default configured to listen only to localhost. That means that default X settings become more and more defensive and thus without tuning there are more and more reasons why remote communications attempts using X initially will fail. That's why the first time you try to run a remote X application on modern Linux distributions, it usually does not work. The most common error message by far is "Can't open display". In this case an X client application, for example xterm, reports an error Can't open display on startup, for instance xterm Xt error: Can't open display: localhost:0.0 The first thing to try is to ensure that you used a correct sequence of commands. One typical mistake is you use like xhost + on the client instead of the server (your workstation). If you have problems the first thing to do is to see the value of the variable DISPLAY on the client. If it is not set at all or set incorrectly you need to fix that, for example export DISPLAY=10.10.10.1:0.0 The second step to check is whether X11 server itself is accessible from the client. If firewall on the server is enables it can block X11 session. You better exclude firewall from the possible causes first. You can see this by using nmap. If port 177 (UDP) or port 6000 (TCP) are blocked you need to fix this fi