DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:references:from:cc:to:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=COG8I85RYr4LoVxc
	F0utKzqbkzPEpvOXNNrn5xYqKPqanPgFNysuNM12Y5uir8b6zaxEDLX/GvOtH13G
	bUvYKR4zNJ24ItNtRvSzkmN2qq9o1+rqwdI+QyFfVus+PvLLE9tNwZuYmHk+rpUt
	lWm91gDej0qRaCSFSkLM3H6D2vs=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Subject: Re: XWin no longer working for me with -nolisten tcp?
References: <58A77737.5070104@gmail.com>
From: Jon Turney <jon.turney@dronecode.org.uk>
Cc: codespunk+cygwin@gmail.com
To: cygwin@cygwin.com
Message-ID: <026e3bfa-8d70-cac9-2e9a-d8707633ea12@dronecode.org.uk>
Date: Tue, 21 Feb 2017 14:27:39 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <58A77737.5070104@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

On 17/02/2017 22:20, Matt D. wrote:
>
> I just recently formatted and reinstalled Windows 10 x64. I have not
> updated anything related to Cygwin and everything version-wise is just
> as it was.
>
> I was previously starting X with the following:
>
> $ xinit -- -multiplemonitors -multiwindow -clipboard -noprimary -dpi 96
> -nolisten tcp -displayfd 3 3>/c/home/.display
>
> But now it fails to open the display:
>
> http://pastebin.com/raw/bLHTWcrS

This log doesn't exactly match that command ('-nolisten inet6' rather 
'-nolisten tcp')

Note that since 1.17.0, -nolisten tcp is the default.

> [ 21352.125] winInitMultiWindowWM - DISPLAY=:0.0
> [ 21352.125] winMultiWindowXMsgProc - DISPLAY=:0.0
> [ 21354.140] winInitMultiWindowWM - Could not open display, try: 1, sleeping: 5
> [ 21354.140] winMultiWindowXMsgProc - Could not open display, try: 1, sleeping: 5
> [ 21361.140] winInitMultiWindowWM - Could not open display, try: 2, sleeping: 5
> [ 21361.140] winMultiWindowXMsgProc - Could not open display, try: 2, sleeping: 5
> [ 21363.671] winDeinitMultiWindowWM - Noting shutdown in progress

This seems to indicate that the helper clients can't connect to the X 
server on the (emulated) unix domain socket, which is causing the X 
server to be stopped.

I can't reproduce this.

Conceivably, this might be caused by firewall issues.

> I can get around this issue by using "-listen tcp" instead of "-nolisten
> tcp" but I don't understand why. This is especially ironic considering

Can you show the log for a working X server as well, please?

> that this is the complete opposite workaround to what I had to use three
> years ago:
>
> https://cygwin.com/ml/cygwin-xfree/2014-07/msg00017.html

-- 
Jon Turney
Volunteer Cygwin/X X Server maintainer

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