Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
comp.os.linux.x
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
Error: no display specified
Options
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
   5 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
T. vor der Brück  
View profile  
 More options Mar 9 2012, 5:25 am
Newsgroups: comp.os.linux.x
From: "T. vor der Brück" <nos...@nospam.de>
Date: Fri, 09 Mar 2012 11:25:55 +0100
Local: Fri, Mar 9 2012 5:25 am
Subject: Error: no display specified
Print | Individual message | Show original | Report this message | Find messages by this author
Hi, together,

I make a remote login and try to start an x application I always get the
error message:
Error: no display specified

I use Debian Squeeze on both machines, the ssh client and the ssh
server, the error must be on the server-side since it works with other
Ubuntu SSH servers with this client. The package xauth is installed on
the server.

I provide the debug output of the ssh client and the sshd_config
Any help would be appreciated.

Tim

shell-debug
=======================================

vorderbr@pc-108-198:~$ ssh -vv -X -l vorderbr pc-108-214
OpenSSH_5.5p1 Debian-6+squeeze1, OpenSSL 0.9.8o 01 Jun 2010
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to pc-108-214 [141.2.108.214] port 22.
debug1: Connection established.
debug1: identity file /home/vorderbr/.ssh/id_rsa type -1
debug1: identity file /home/vorderbr/.ssh/id_rsa-cert type -1
debug1: identity file /home/vorderbr/.ssh/id_dsa type -1
debug1: identity file /home/vorderbr/.ssh/id_dsa-cert type -1
debug1: Remote protocol version 2.0, remote software version
OpenSSH_5.5p1 Debian-6+squeeze1
debug1: match: OpenSSH_5.5p1 Debian-6+squeeze1 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.5p1 Debian-6+squeeze1
debug2: fd 3 setting O_NONBLOCK
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug2: kex_parse_kexinit:
diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,dif fie-hellman-group14-sha1,diffie-hellman-group1-sha1
debug2: kex_parse_kexinit:
ssh-rsa-cert-...@openssh.com,ssh-dss-cert-...@openssh.com,ssh-rsa,ssh-dss
debug2: kex_parse_kexinit:
aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc, blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-...@lysator.liu.se
debug2: kex_parse_kexinit:
aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc, blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-...@lysator.liu.se
debug2: kex_parse_kexinit:
hmac-md5,hmac-sha1,umac...@openssh.com,hmac-ripemd160,hmac-ripemd...@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit:
hmac-md5,hmac-sha1,umac...@openssh.com,hmac-ripemd160,hmac-ripemd...@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: none,z...@openssh.com,zlib
debug2: kex_parse_kexinit: none,z...@openssh.com,zlib
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit: first_kex_follows 0
debug2: kex_parse_kexinit: reserved 0
debug2: kex_parse_kexinit:
diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,dif fie-hellman-group14-sha1,diffie-hellman-group1-sha1
debug2: kex_parse_kexinit: ssh-rsa,ssh-dss
debug2: kex_parse_kexinit:
aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc, blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-...@lysator.liu.se
debug2: kex_parse_kexinit:
aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc, blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-...@lysator.liu.se
debug2: kex_parse_kexinit:
hmac-md5,hmac-sha1,umac...@openssh.com,hmac-ripemd160,hmac-ripemd...@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit:
hmac-md5,hmac-sha1,umac...@openssh.com,hmac-ripemd160,hmac-ripemd...@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: none,z...@openssh.com
debug2: kex_parse_kexinit: none,z...@openssh.com
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit: first_kex_follows 0
debug2: kex_parse_kexinit: reserved 0
debug2: mac_setup: found hmac-md5
debug1: kex: server->client aes128-ctr hmac-md5 none
debug2: mac_setup: found hmac-md5
debug1: kex: client->server aes128-ctr hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug2: dh_gen_key: priv key bits set: 130/256
debug2: bits set: 537/1024
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host 'pc-108-214' is known and matches the RSA host key.
debug1: Found key in /home/vorderbr/.ssh/known_hosts:1
debug2: bits set: 513/1024
debug1: ssh_rsa_verify: signature correct
debug2: kex_derive_keys
debug2: set_newkeys: mode 1
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug2: set_newkeys: mode 0
debug1: SSH2_MSG_NEWKEYS received
debug1: Roaming not allowed by server
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug2: key: /home/vorderbr/.ssh/id_rsa ((nil))
debug2: key: /home/vorderbr/.ssh/id_dsa ((nil))
debug1: Authentications that can continue: publickey,password
debug1: Next authentication method: publickey
debug1: Trying private key: /home/vorderbr/.ssh/id_rsa
debug1: Trying private key: /home/vorderbr/.ssh/id_dsa
debug2: we did not send a packet, disable method
debug1: Next authentication method: password
vorderbr@pc-108-214's password:
debug2: we sent a password packet, wait for reply
debug1: Authentication succeeded (password).
debug1: channel 0: new [client-session]
debug2: channel 0: send open
debug1: Requesting no-more-sessi...@openssh.com
debug1: Entering interactive session.
debug2: callback start
debug2: x11_get_proto: /usr/bin/xauth  list :0.0 2>/dev/null
debug1: Requesting X11 forwarding with authentication spoofing.
debug2: channel 0: request x11-req confirm 0
debug2: client_session2_setup: id 0
debug2: channel 0: request pty-req confirm 1
debug1: Sending environment.
debug1: Sending env LANG = de_DE.utf8
debug2: channel 0: request env confirm 0
debug2: channel 0: request shell confirm 1
debug2: fd 3 setting TCP_NODELAY
debug2: callback done
debug2: channel 0: open confirm rwindow 0 rmax 32768
debug2: channel_input_status_confirm: type 99 id 0
debug2: PTY allocation request accepted on channel 0
debug2: channel 0: rcvd adjust 2097152
debug2: channel_input_status_confirm: type 99 id 0
debug2: shell request accepted on channel 0
Linux pc-108-214 2.6.39-bpo.2-amd64 #1 SMP Tue Jul 26 10:35:23 UTC 2011
x86_64

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
You have new mail.
Last login: Fri Mar  9 12:17:57 2012 from pc-108-198
vorderbr@pc-108-214:~$ firefox
Error: no display specified
vorderbr@pc-108-214:~$ debug2: client_check_window_change: changed
debug2: channel 0: request window-change confirm 0
vorderbr@pc-108-214:~$ debug2: client_check_window_change: changed
debug2: channel 0: request window-change confirm 0
vorderbr@pc-108-214:~$ debug2: client_check_window_change: changed
debug2: channel 0: request window-change confirm 0
vorderbr@pc-108-214:~$ debug2: client_check_window_change: changed
debug2: channel 0: request window-change confirm 0
vorderbr@pc-108-214:~$ debug2: client_check_window_change: changed
debug2: channel 0: request window-change confirm 0
vorderbr@pc-108-214:~$ debug2: client_check_window_change: changed
debug2: channel 0: request window-change confirm 0
vorderbr@pc-108-214:~$ debug2: client_check_window_change: changed
debug2: channel 0: request window-change confirm 0
vorderbr@pc-108-214:~$ debug2: client_check_window_change: changed
debug2: channel 0: request window-change confirm 0
vorderbr@pc-108-214:~$ debug2: client_check_window_change: changed
debug2: channel 0: request window-change confirm 0
vorderbr@pc-108-214:~$ debug2: client_check_window_change: changed
debug2: channel 0: request window-change confirm 0
vorderbr@pc-108-214:~$ debug2: client_check_window_change: changed
debug2: channel 0: request window-change confirm 0
vorderbr@pc-108-214:~$ debug2: client_check_window_change: changed
debug2: channel 0: request window-change confirm 0
vorderbr@pc-108-214:~$ debug2: client_check_window_change: changed
debug2: channel 0: request window-change confirm 0
vorderbr@pc-108-214:~$ debug2: client_check_window_change: changed
debug2: channel 0: request window-change confirm 0
vorderbr@pc-108-214:~$ debug2: client_check_window_change: changed
debug2: channel 0: request window-change confirm 0
vorderbr@pc-108-214:~$ debug2: client_check_window_change: changed
debug2: channel 0: request window-change confirm 0
vorderbr@pc-108-214:~$ debug2: client_check_window_change: changed
debug2: channel 0: request window-change confirm 0
vorderbr@pc-108-214:~$ debug2: client_check_window_change: changed
debug2: channel 0: request window-change confirm 0
vorderbr@pc-108-214:~$ debug2: client_check_window_change: changed
debug2: channel 0: request window-change confirm 0
vorderbr@pc-108-214:~$ debug2: client_check_window_change: changed
debug2: channel 0: request window-change confirm 0
vorderbr@pc-108-214:~$ debug2: client_check_window_change: changed
debug2: channel 0: request window-change confirm 0
vorderbr@pc-108-214:~$ debug2: client_check_window_change: changed
debug2: channel 0: request window-change confirm 0
vorderbr@pc-108-214:~$ debug2: client_check_window_change: changed
debug2: channel 0: request window-change confirm 0
vorderbr@pc-108-214:~$ debug2: client_check_window_change: changed
debug2: channel 0: request window-change confirm 0
vorderbr@pc-108-214:~$ debug2: client_check_window_change: changed
debug2: channel 0: request window-change confirm 0
vorderbr@pc-108-214:~$ debug2: client_check_window_change: changed
debug2: channel 0: request window-change confirm 0
vorderbr@pc-108-214:~$ debug2: client_check_window_change: changed
debug2: channel 0: request window-change confirm 0

sshd config ...

read more »


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Aragorn  
View profile  
 More options Mar 9 2012, 11:58 am
Newsgroups: comp.os.linux.x
Followup-To: comp.os.linux.x
From: Aragorn <stry...@telenet.be.invalid>
Date: Fri, 09 Mar 2012 17:58:31 +0100
Local: Fri, Mar 9 2012 11:58 am
Subject: Re: Error: no display specified
Print | Individual message | Show original | Report this message | Find messages by this author
On Friday 09 March 2012 11:25, T. vor der Brück conveyed the following
to comp.os.linux.x...

> Hi, together,

> I make a remote login and try to start an x application I always get
> the error message:
> Error: no display specified

> [...]

You have to export the DISPLAY variable on the remote machine so that it
points to your local machine's DISPLAY, and you must do this _before_
attempting to run a remote X application.  

For instance...

    export DISPLAY=192.168.0.1:0.0
                   ----------- - -
                         |     | |_ port on the local video adapter
                         |     |___ local video adapter
                         |_________ local IP address or hostname

Hope this helps. ;-)

--
= Aragorn =
(registered GNU/Linux user #223157)


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Richard Kettlewell  
View profile  
 More options Mar 9 2012, 12:11 pm
Newsgroups: comp.os.linux.x
From: Richard Kettlewell <r...@greenend.org.uk>
Date: Fri, 09 Mar 2012 17:11:45 +0000
Local: Fri, Mar 9 2012 12:11 pm
Subject: Re: Error: no display specified
Print | Individual message | Show original | Report this message | Find messages by this author
"T. vor der Brück" <nos...@nospam.de> writes:

> debug2: x11_get_proto: /usr/bin/xauth  list :0.0 2>/dev/null
> debug1: Requesting X11 forwarding with authentication spoofing.
> debug2: channel 0: request x11-req confirm 0

The client has certainly asked for X11 forwarding.

> Linux pc-108-214 2.6.39-bpo.2-amd64 #1 SMP Tue Jul 26 10:35:23 UTC
> 2011 x86_64

> The programs included with the Debian GNU/Linux system are free software;
> the exact distribution terms for each program are described in the
> individual files in /usr/share/doc/*/copyright.

> Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
> permitted by applicable law.
> You have new mail.
> Last login: Fri Mar  9 12:17:57 2012 from pc-108-198
> vorderbr@pc-108-214:~$ firefox
> Error: no display specified

Is DISPLAY set or not at this point?

If not, is it possible that it's been modified in one of the shell
startup files?

> sshd config

Just to be clear, that is the server's sshd_config?

--
http://www.greenend.org.uk/rjk/


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Richard Kettlewell  
View profile  
 More options Mar 9 2012, 12:12 pm
Newsgroups: comp.os.linux.x
From: Richard Kettlewell <r...@greenend.org.uk>
Date: Fri, 09 Mar 2012 17:12:10 +0000
Local: Fri, Mar 9 2012 12:12 pm
Subject: Re: Error: no display specified
Print | Individual message | Show original | Report this message | Find messages by this author

He's trying to use X11 forwarding, which does not in general need anyone
to mess around with DISPLAY variables.

--
http://www.greenend.org.uk/rjk/


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
John McCue  
View profile  
 More options Mar 11 2012, 2:06 pm
Newsgroups: comp.os.linux.x
From: John McCue <jmc...@jmclin0.hsd1.ma.comcast.net>
Date: Sun, 11 Mar 2012 18:06:16 +0000 (UTC)
Local: Sun, Mar 11 2012 2:06 pm
Subject: Re: Error: no display specified
Print | Individual message | Show original | Report this message | Find messages by this author
"T. vor der Bruck" <nos...@nospam.de> wrote:

> Hi, together,

> I make a remote login and try to start an x application I always get the
> error message:
> Error: no display specified

<snip>

Hi,

Give this a try:

1. add the 2 lines below to /etc/ssh/sshd_config

Match User <USERID>
        X11Forwarding yes

2. execute
       ssh -Y <USERID>@<SYS_NAME> -X
   and see if it works, ssh will take care of DISPLAY

<USERID> =your user id
<SYS_NAME> = your remote system

HTH
John


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google