Cygwin Error No Display Specified
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss cygwin error can't open display the workings and policies of this site About Us Learn more about
Error No Display Specified Selenium
Stack Overflow the company Business Learn more about hiring developers or posting ads with us Unix & Linux
Error No Display Specified Centos
Questions Tags Users Badges 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.
Error No Display Specified X11
Join 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 why won't x11 display work through ssh login? up vote 3 down vote favorite 2 I have logged in to a remote server and am trying to display firefox error no display specified an x application(e.g. firefox). but an error message appears. the below are my attempts to open firefox Black@Black-PC ~ $ ssh -X kwagjj@$labserver -p 122 [kwagjj@James5 ~]$ firefox Error: no display specified [kwagjj@James5 ~]$ exit logout Connection to 143.248.146.204 closed. Black@Black-PC ~ $ ssh -Y kwagjj@$labserver -p 122 [kwagjj@James5 ~]$ firefox Error: no display specified [kwagjj@James5 ~]$ I used -X, -Y because I read somewhere that these two options are related with credentials regarding X11 and these switches will do the job for me. Even without the -X, -Y switches, my attempt failed. What does the 'no display speicified' error mean? P.S. The weird thing is that if I connect to the remote server through my PUTTY and repeat the command 'firefox' it works?!?!(firefox is displayed on local computer) P.S. my local computer is Windows 7 so I have Xming running on background in order to allow X11 display. As for the attempt written on the upper part, the commands were typed in at Cygwin terminal. ssh x11 cygwin share|improve this question edited Jun 24 '14 at
any other X Server.
It is recommended that you use the secure method of tunnelling the X connection over ssh. Alternatively, you can use the host-based access firefox error no display specified redhat control provided by the X server, connecting to the remote machine using linux error no display specified telnet or rsh and directing clients to connect to the server by setting the DISPLAY environment variable. xming error no display specified This method is insecure and not recommended.Secure sshOn your Windows machine:Make sure you have the openssh package installed.Launch Cygwin/XEnsure the DISPLAY http://unix.stackexchange.com/questions/138936/why-wont-x11-display-work-through-ssh-login environment variable is set correctly. (This step is not neccessary if you are entering your commands into an X terminal, as DISPLAY must already be set in that case) $ export DISPLAY=:0.0 Run the ssh command to connect to the remote host: $ ssh -Y username@remote_hostname_or_ip_address http://x.cygwin.com/docs/ug/using-remote-apps.html >Enter your password when prompted by ssh.Your ssh session should now show you a shell prompt for your remote machine.Note: The ssh server will automatically set the DISPLAY environment variable appropriately, typically to something like localhost:10.0, so clients will connect to a proxy X11 display on the remote host from which the X11 protocol will be forwarded over ssh to your X server. If your login scripts unconditionally set DISPLAY to something else, this will break X11 forwarding.Pages: 1 #1 2010-01-16 21:58:52 Wen Member From: Oslo, Norway Registered: 2008-10-02 Posts: 31 [Solved]Can't forward X in ssh with "X11Forwarding yes" set Hi friends,I can't forward X in ssh, https://bbs.archlinux.org/viewtopic.php?id=88945 even with "X11Forwarding yes" set. After I ssh -X into the server, http://serverfault.com/questions/357261/cant-start-remote-gui-programs-on-centos-6 it prompts every time when I try to run a graphic app:Error: no display specifiedCould you please give me a hint? My sshd_config of the server is attached:# $OpenBSD: sshd_config,v 1.80 2008/07/02 02:24:18 djm Exp $ # This is the sshd server system-wide configuration file. See # sshd_config(5) for error no more information. # This sshd was compiled with PATH=/usr/bin:/bin:/usr/sbin:/sbin # The strategy used for options in the default sshd_config shipped with # OpenSSH is to specify options with their default value where # possible, but leave them commented. Uncommented options change a # default value. #Port 22 #AddressFamily any #ListenAddress 0.0.0.0 #ListenAddress :: # Disable legacy (protocol version 1) support error no display in the server for new # installations. In future the default will change to require explicit # activation of protocol 1 Protocol 2 # HostKey for protocol version 1 #HostKey /etc/ssh/ssh_host_key # HostKeys for protocol version 2 #HostKey /etc/ssh/ssh_host_rsa_key #HostKey /etc/ssh/ssh_host_dsa_key # Lifetime and size of ephemeral version 1 server key #KeyRegenerationInterval 1h #ServerKeyBits 1024 # Logging # obsoletes QuietMode and FascistLogging #SyslogFacility AUTH #LogLevel INFO # Authentication: #LoginGraceTime 2m #PermitRootLogin yes #StrictModes yes #MaxAuthTries 6 #MaxSessions 10 #RSAAuthentication yes #PubkeyAuthentication yes #AuthorizedKeysFile .ssh/authorized_keys # For this to work you will also need host keys in /etc/ssh/ssh_known_hosts #RhostsRSAAuthentication no # similar for protocol version 2 #HostbasedAuthentication no # Change to yes if you don't trust ~/.ssh/known_hosts for # RhostsRSAAuthentication and HostbasedAuthentication #IgnoreUserKnownHosts no # Don't read the user's ~/.rhosts and ~/.shosts files #IgnoreRhosts yes # To disable tunneled clear text passwords, change to no here! PasswordAuthentication no #PermitEmptyPasswords no # Change to no to disable s/key passwords #ChallengeResponseAuthentication no # Kerberos options #KerberosAuthentication no #KerberosOrLocalPasswd yes #KerberosTicketCleanup yes #KerberosGetAFSToken no # GSSAPI options #GSSAPIAuthentication no #GSSAPICleanupCredentials yes # Set th
Start 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 hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join 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 Can't start remote GUI programs on CentOS 6 [closed] up vote 1 down vote favorite 3 I have set ForwardX11 yes in /etc/ssh/ssh_config which normally enables me to open GUI programs on CentOS5 by ssh -X server But doing the same on CentOS6 I get # firefox -no-remote Error: no display specified # What could be wrong? Update Have tried the following # firefox -no-remote Error: no display specified # echo $DISPLAY # export DISPLAY=localhost:0.0 # echo $DISPLAY localhost:0.0 # firefox -no-remote Error: cannot open display: localhost:0.0 # Update 2 ~$ echo $DISPLAY :0.0 ~$ export DISPLAY=localhost:0.0 ~$ ssh -X root@net2 [root@net2 ~]# xclock Error: Can't open display: [root@net2 ~]# linux centos share|improve this question edited Feb 7 '12 at 10:10 asked Feb 6 '12 at 15:59 Sandra 3,6861856116 closed as off-topic by Magellan, Jenny D, mdpc, Nathan C, Scott Pack Oct 11 '13 at 0:57 This question appears to be off-topic. The users who voted to close gave this specific reason:"Questions must demonstrate a minimal understanding of the problem being solved. Try including attempted solutions, why they didn't work, and the expected results. See How can I ask better questions on Server Fault? for further guidance." – Magellan, Jenny D, mdpc, Nathan C, Scott PackIf this question can be reworded to fit the rules in the help center, please edit the question. add a comment| 2 Answers 2 active oldest votes up vote 9 down vote accepted After changing the ForwardX11 to yes, have you restarted the sshd server? That is, by typing: # /etc/init.d/sshd restart Also you might try getting something simpler like xclock working first, to isolate whether it's firefox related (to prove at least your remote X11 is working fine). # /usr/bin/xclock & You might need to install it first. # yum