X server shutdown or killed/destroyed

X server shutdown or killed/destroyed

[Howard Feil]

I have installed cygwin on several windows XP 32bit machines.  To do the install I used the defaults and then installed all of X11 and 
Networks.  After a little while when opening a new windows, I get the 
error:


The application 'gedit' lost its connection to the display localhost:11.0;
most likely the X server was shut down or you killed/destroyed
the application.

It doesn't matter what I do next, nothing simple makes the x-server come back alive.  

This
 is happening on multiple machines.  For some reasons I have other 
machines that never have a problem.  These machines may have older 
installations.


Any advice is appreciated.

Howard

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/

Re: X server shutdown or killed/destroyed

[Jon TURNEY]

On 26/07/2011 14:20, Howard Feil wrote:
> I have installed cygwin on several windows XP 32bit machines.  To do the install I used the defaults and then installed all of X11 and
> Networks.  After a little while

about 20 minutes?

 > when opening a new windows, I get the
> error:
>
>
> The application 'gedit' lost its connection to the display localhost:11.0;
> most likely the X server was shut down or you killed/destroyed
> the application.
>
> It doesn't matter what I do next, nothing simple makes the x-server come back alive.
>
> This
>   is happening on multiple machines.  For some reasons I have other
> machines that never have a problem.  These machines may have older
> installations.
>
>
> Any advice is appreciated.

Use ssh -Y

[1] http://cygwin.com/ml/cygwin/2011-05/msg00394.html

-- 
Jon TURNEY
Volunteer Cygwin/X X Server maintainer

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/

Re: X server shutdown or killed/destroyed

[Jon TURNEY]

On 29/07/2011 15:27, Howard Feil wrote:
>
> Thanks for the reply.
>
> So far ssh -Y seems to be doing the trick.

Good.

I'd like to know a bit more about why this is happening, though, so if you 
could share the OS and sshd version which is running on the machine you are 
sshd-ing to, and the output when you connect using ssh -vvv -X, that would be 
interesting.

> On 26/07/2011 14:20, Howard Feil wrote:
>> I have installed cygwin on several windows XP 32bit machines.  To do the install I used the defaults and then installed all of X11 and
>> Networks.  After a little while
>
> about 20 minutes?
>
>> when opening a new windows, I get the
>> error:
>>
>>
>> The application 'gedit' lost its connection to the display localhost:11.0;
>> most likely the X server was shut down or you killed/destroyed
>> the application.
>>
>> It doesn't matter what I do next, nothing simple makes the x-server come back alive.
>>
>> This
>>     is happening on multiple machines.  For some reasons I have other
>> machines that never have a problem.  These machines may have older
>> installations.
>>
>>
>> Any advice is appreciated.
>
> Use ssh -Y
>
> [1] http://cygwin.com/ml/cygwin/2011-05/msg00394.html

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/

Re: X server shutdown or killed/destroyed

[Howard Feil]

Sorry about the slow reply. 


The OS of the target machines was CENTOS 5.5 and 5.4

[root@MQWKS4 ~]# ssh -V
OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008


$ ssh -vvv -X feilh@mqwks4
OpenSSH_5.8p1, OpenSSL 0.9.8r 8 Feb 2011
debug2: ssh_connect: needpriv 0
debug1: Connecting to mqwks4 [10.16.72.11] port 22.
debug1: Connection established.
debug1: identity file /home/hf21548/.ssh/id_rsa type -1
debug1: identity file /home/hf21548/.ssh/id_rsa-cert type -1
debug1: identity file /home/hf21548/.ssh/id_dsa type -1
debug1: identity file /home/hf21548/.ssh/id_dsa-cert type -1
debug1: identity file /home/hf21548/.ssh/id_ecdsa type -1
debug1: identity file /home/hf21548/.ssh/id_ecdsa-cert type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_4.3
debug1: match: OpenSSH_4.3 pat OpenSSH_4*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.8
debug2: fd 3 setting O_NONBLOCK
debug3: load_hostkeys: loading entries for host "mqwks4" from file "/home/hf21548/.ssh/known_hosts"
debug3: load_hostkeys: found key type RSA in file /home/hf21548/.ssh/known_hosts:1
debug3: load_hostkeys: loaded 1 keys
debug3: order_hostkeyalgs: prefer hostkeyalgs: ssh-rsa-cert-v01@openssh.com,ssh-rsa-cert-v00@openssh.com,ssh-rsa
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug2: kex_parse_kexinit: ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
debug2: kex_parse_kexinit: ssh-rsa-cert-v01@openssh.com,ssh-rsa-cert-v00@openssh.com,ssh-rsa,ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ssh-dss-cert-v01@openssh.com,ssh-dss-cert-v00@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,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-cbc@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-cbc@lysator.liu.se
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: none,zlib@openssh.com,zlib
debug2: kex_parse_kexinit: none,zlib@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-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
debug2: kex_parse_kexinit: ssh-rsa,ssh-dss
debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: none,zlib@openssh.com
debug2: kex_parse_kexinit: none,zlib@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: 132/256
debug2: bits set: 505/1024
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Server host key: RSA 78:f3:28:01:c8:0d:47:46:05:db:95:d3:8a:f0:b0:c5
debug3: load_hostkeys: loading entries for host "mqwks4" from file "/home/hf21548/.ssh/known_hosts"
debug3: load_hostkeys: found key type RSA in file /home/hf21548/.ssh/known_hosts:1
debug3: load_hostkeys: loaded 1 keys
debug3: load_hostkeys: loading entries for host "10.16.72.11" from file "/home/hf21548/.ssh/known_hosts"
debug3: load_hostkeys: found key type RSA in file /home/hf21548/.ssh/known_hosts:1
debug3: load_hostkeys: loaded 1 keys
debug1: Host 'mqwks4' is known and matches the RSA host key.
debug1: Found key in /home/hf21548/.ssh/known_hosts:1
debug2: bits set: 523/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/hf21548/.ssh/id_rsa (0x0)
debug2: key: /home/hf21548/.ssh/id_dsa (0x0)
debug2: key: /home/hf21548/.ssh/id_ecdsa (0x0)
debug1: Authentications that can continue: publickey,gssapi-with-mic,password
debug3: start over, passed a different list publickey,gssapi-with-mic,password
debug3: preferred publickey,keyboard-interactive,password
debug3: authmethod_lookup publickey
debug3: remaining preferred: keyboard-interactive,password
debug3: authmethod_is_enabled publickey
debug1: Next authentication method: publickey
debug1: Trying private key: /home/hf21548/.ssh/id_rsa
debug3: no such identity: /home/hf21548/.ssh/id_rsa
debug1: Trying private key: /home/hf21548/.ssh/id_dsa
debug3: no such identity: /home/hf21548/.ssh/id_dsa
debug1: Trying private key: /home/hf21548/.ssh/id_ecdsa
debug3: no such identity: /home/hf21548/.ssh/id_ecdsa
debug2: we did not send a packet, disable method
debug3: authmethod_lookup password
debug3: remaining preferred: ,password
debug3: authmethod_is_enabled password
debug1: Next authentication method: password
feilh@mqwks4's password: 
debug3: packet_send2: adding 64 (len 59 padlen 5 extra_pad 64)
debug2: we sent a password packet, wait for reply
debug1: Authentication succeeded (password).
Authenticated to mqwks4 ([10.16.72.11]:22).
debug1: channel 0: new [client-session]
debug3: ssh_session2_open: channel_new: 0
debug2: channel 0: send open
debug1: Entering interactive session.
debug2: callback start
debug2: x11_get_proto: /usr/bin/xauth -f /tmp/ssh-IFVizRlT6060/xauthfile generate :0.0 MIT-MAGIC-COOKIE-1 untrusted timeout 1200 2>/dev/null
Warning: untrusted X11 forwarding setup failed: xauth key data not generated
Warning: No xauth data; using fake authentication data for X11 forwarding.
debug1: Requesting X11 forwarding with authentication spoofing.
debug2: channel 0: request x11-req confirm 0
debug2: client_session2_setup: id 0
debug2: fd 3 setting TCP_NODELAY
debug3: packet_set_tos: set IP_TOS 0x10
debug2: channel 0: request pty-req confirm 1
debug2: channel 0: request shell confirm 1
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
Last login: Thu Jul 28 12:18:59 2011 from abg743.aero.org
MQWKS4:~> 




Sent: Monday, August 1, 2011 2:43 PM
Subject: Re: X server shutdown or killed/destroyed

On 29/07/2011 15:27, Howard Feil wrote:
>
> Thanks for the reply.
>
> So far ssh -Y seems to be doing the trick.

Good.

I'd like to know a bit more about why this is happening, though, so if you 
could share the OS and sshd version which is running on the machine you are 
sshd-ing to, and the output when you connect using ssh -vvv -X, that would be 
interesting.

> On 26/07/2011 14:20, Howard Feil wrote:
>> I have installed cygwin on several windows XP 32bit machines.  To do the install I used the defaults and then installed all of X11 and
>> Networks.  After a little while
>
> about 20 minutes?
>
>> when opening a new windows, I get the
>> error:
>>
>>
>> The application 'gedit' lost its connection to the display localhost:11.0;
>> most likely the X server was shut down or you killed/destroyed
>> the application.
>>
>> It doesn't matter what I do next, nothing simple makes the x-server come back alive.
>>
>> This
>>     is happening on multiple machines.  For some reasons I have other
>> machines that never have a problem.  These machines may have older
>> installations.
>>
>>
>> Any advice is appreciated.
>
> Use ssh -Y
>
> [1] http://cygwin.com/ml/cygwin/2011-05/msg00394.html


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/

Re: X server shutdown or killed/destroyed

[Jon TURNEY]

On 08/08/2011 17:49, Howard Feil wrote:
> The OS of the target machines was CENTOS 5.5 and 5.4
>
> [root@MQWKS4 ~]# ssh -V
> OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008
[logs snipped]

Thanks very much for the information. I am now able to reproduce this issue.

This appears to be a change in the ssh client so that ForwardX11Timeout 
applies, even if untrusted authentication cookie generation failed (See [1]).

It looks like this change first appeared in openssh 5.6, although I can't see 
it mentioned in the announce email.

Note that if you had run ssh -v, you should have got a "Rejected X11 
connection after ForwardX11Timeout expired" explaining what was happening :-)

I guess I'll add something in the Cygwin/X FAQ about this.

[1] 
http://www.openbsd.org/cgi-bin/cvsweb/src/usr.bin/ssh/clientloop.c.diff?r1=1.220;r2=1.221;f=h

> Sent: Monday, August 1, 2011 2:43 PM
> Subject: Re: X server shutdown or killed/destroyed
>
> On 29/07/2011 15:27, Howard Feil wrote:
>>
>> Thanks for the reply.
>>
>> So far ssh -Y seems to be doing the trick.
>
> Good.
>
> I'd like to know a bit more about why this is happening, though, so if you
> could share the OS and sshd version which is running on the machine you are
> sshd-ing to, and the output when you connect using ssh -vvv -X, that would be
> interesting.
>
>> On 26/07/2011 14:20, Howard Feil wrote:
>>> I have installed cygwin on several windows XP 32bit machines.  To do the install I used the defaults and then installed all of X11 and
>>> Networks.  After a little while
>>
>> about 20 minutes?
>>
>>> when opening a new windows, I get the
>>> error:
>>>
>>>
>>> The application 'gedit' lost its connection to the display localhost:11.0;
>>> most likely the X server was shut down or you killed/destroyed
>>> the application.
>>>
>>> It doesn't matter what I do next, nothing simple makes the x-server come back alive.
>>>
>>> This
>>>       is happening on multiple machines.  For some reasons I have other
>>> machines that never have a problem.  These machines may have older
>>> installations.
>>>
>>>
>>> Any advice is appreciated.
>>
>> Use ssh -Y
>>
>> [1] http://cygwin.com/ml/cygwin/2011-05/msg00394.html

-- 
Jon TURNEY
Volunteer Cygwin/X X Server maintainer

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/

Re: X server shutdown or killed/destroyed

[Lester Ingber]

Jon TURNEY <jon.turney <at> dronecode.org.uk> writes:

> 
> On 08/08/2011 17:49, Howard Feil wrote:
> > The OS of the target machines was CENTOS 5.5 and 5.4
> >
> > [root <at> MQWKS4 ~]# ssh -V
> > OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008
> [logs snipped]
> 
> Thanks very much for the information. I am now able to reproduce this issue.
> 
> This appears to be a change in the ssh client so that ForwardX11Timeout 
> applies, even if untrusted authentication cookie generation failed (See [1]).
> 
> It looks like this change first appeared in openssh 5.6, although I can't see 
> it mentioned in the announce email.
> 
> Note that if you had run ssh -v, you should have got a "Rejected X11 
> connection after ForwardX11Timeout expired" explaining what was happening 
> 
> I guess I'll add something in the Cygwin/X FAQ about this.

Is there a work-around for this problem?  I (too) often get timed out when 
ssh'ing into sites on which I need X-windows (so I use ssh -Y).  I have no such 
problems when using a non-X console to ssh into these sites.

Thanks.

Lester



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/