From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin@cygwin.com
Cc: codespunk+cygwin@gmail.com
Subject: Re: XWin no longer working for me with -nolisten tcp?
Date: Tue, 21 Feb 2017 14:27:00 -0000 [thread overview]
Message-ID: <026e3bfa-8d70-cac9-2e9a-d8707633ea12@dronecode.org.uk> (raw)
In-Reply-To: <58A77737.5070104@gmail.com>
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
prev parent reply other threads:[~2017-02-21 14:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 22:20 Matt D.
2017-02-17 22:38 ` Matt D.
2017-02-18 14:50 ` cyg Simple
2017-02-21 14:27 ` Jon Turney [this message]
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=026e3bfa-8d70-cac9-2e9a-d8707633ea12@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=codespunk+cygwin@gmail.com \
--cc=cygwin@cygwin.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).