From: "Matt D." <matt@codespunk.com>
To: cygwin@cygwin.com
Subject: Re: XWin no longer working for me with -nolisten tcp?
Date: Fri, 17 Feb 2017 22:38:00 -0000 [thread overview]
Message-ID: <58A77B77.7090603@codespunk.com> (raw)
In-Reply-To: <58A77737.5070104@gmail.com>
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
next prev parent reply other threads:[~2017-02-17 22:38 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. [this message]
2017-02-18 14:50 ` cyg Simple
2017-02-21 14:27 ` Jon Turney
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=58A77B77.7090603@codespunk.com \
--to=matt@codespunk.com \
--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).