public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Jon TURNEY <jon.turney@dronecode.org.uk>
To: cygwin-xfree@cygwin.com
Cc: Howard Feil <hiking_feil@yahoo.com>
Subject: Re: X server shutdown or killed/destroyed
Date: Wed, 10 Aug 2011 12:10:00 -0000	[thread overview]
Message-ID: <4E427543.6060205@dronecode.org.uk> (raw)
In-Reply-To: <1312822191.2359.YahooMailNeo@web161421.mail.bf1.yahoo.com>

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/


  reply	other threads:[~2011-08-10 12:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-28 15:33 Howard Feil
2011-07-28 15:47 ` Jon TURNEY
     [not found]   ` <1311949646.24780.YahooMailNeo@web161423.mail.bf1.yahoo.com>
2011-08-01 18:44     ` Jon TURNEY
     [not found]       ` <1312819650.57882.YahooMailNeo@web161424.mail.bf1.yahoo.com>
2011-08-08 20:46         ` Howard Feil
2011-08-10 12:10           ` Jon TURNEY [this message]
2012-05-15 21:50             ` Lester Ingber

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E427543.6060205@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-xfree@cygwin.com \
    --cc=hiking_feil@yahoo.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).