* XWin no longer working for me with -nolisten tcp?
@ 2017-02-17 22:20 Matt D.
2017-02-17 22:38 ` Matt D.
2017-02-21 14:27 ` Jon Turney
0 siblings, 2 replies; 4+ messages in thread
From: Matt D. @ 2017-02-17 22:20 UTC (permalink / raw)
To: cygwin
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
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
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
Matt D.
--
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: XWin no longer working for me with -nolisten tcp?
2017-02-17 22:20 XWin no longer working for me with -nolisten tcp? Matt D.
@ 2017-02-17 22:38 ` Matt D.
2017-02-18 14:50 ` cyg Simple
2017-02-21 14:27 ` Jon Turney
1 sibling, 1 reply; 4+ messages in thread
From: Matt D. @ 2017-02-17 22:38 UTC (permalink / raw)
To: cygwin
This workaround I mentioned only appears to work for my local X session.
For example, I can open a local xterm from Cygwin:
$ xterm
But once I connect elsewhere:
$ ssh me@somewhere -Y
I get the following error when trying to bring up an xterm:
$ xterm
connect /tmp/.X11-unix/X0: Permission denied
xterm: Xt error: Can't open display: localhost:10.0
I tried purging /tmp on Cygwin but to no avail.
Note that the server I am connecting to has not been rebooted in months
and nothing has changed there.
Matt D.
On 2/17/2017 2:20 PM, 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
>
> 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
> 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
>
>
> Matt D.
>
--
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: XWin no longer working for me with -nolisten tcp?
2017-02-17 22:20 XWin no longer working for me with -nolisten tcp? Matt D.
2017-02-17 22:38 ` Matt D.
@ 2017-02-21 14:27 ` Jon Turney
1 sibling, 0 replies; 4+ messages in thread
From: Jon Turney @ 2017-02-21 14:27 UTC (permalink / raw)
To: cygwin; +Cc: codespunk+cygwin
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
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2017-02-21 14:27 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-02-17 22:20 XWin no longer working for me with -nolisten tcp? Matt D.
2017-02-17 22:38 ` Matt D.
2017-02-18 14:50 ` cyg Simple
2017-02-21 14:27 ` Jon Turney
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).