public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin-xfree@cygwin.com
Subject: Re: Can't open display with PuTTY and xinit 1.3.4-1
Date: Mon, 05 Jan 2015 17:31:00 -0000 [thread overview]
Message-ID: <54AACA74.3080201@cygwin.com> (raw)
In-Reply-To: <54AA7624.1050205@blankersfamily.com>
On 2015-01-05 05:31, Laurens Blankers wrote:
> When using PuTTY with X11 forwarding enabled X clients are no longer
> able to connect to the X server running locally. When reverting back to
> 1.3.2-1 the problem goes away.
>
> This may be related to the -nolisten tcp which is now the default[1]. If
> this is indeed the case it would be create of adding the '-listen' flag
> to startxwin could be added to the FAQ. Or another, more secure,
> solution would also be appreciated.
Wait, are you talking about a Windows version of PuTTY? Then that makes
sense, as it would be unable of using the *NIX socket typically used by
local X clients, and I am indeed able to duplicate that behaviour. I
can't think of an alternative to -listen if you wish to use a Windows
PuTTY (or, for that matter, any MinGW-compiled X client) with Cygwin/X.
This will be added to the FAQ in due course.
However, a Cygwin PuTTY does not have that limitation, and X11
forwarding works just fine as is. (If there is interest, I can easily
add this to the distribution.) Similarly, the Cygwin (open)ssh
obviously has no problems with X11 forwarding either.
BTW, reverting this behaviour isn't an option either, as it will
actually become the upstream default in the next major release of the X
server.
HTH,
Yaakov
--
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/
next prev parent reply other threads:[~2015-01-05 17:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 11:32 Laurens Blankers
2015-01-05 17:31 ` Yaakov Selkowitz [this message]
2015-01-06 9:12 ` Laurens Blankers
2015-02-24 16:55 Fj
2015-02-24 21:00 ` 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=54AACA74.3080201@cygwin.com \
--to=yselkowitz@cygwin.com \
--cc=cygwin-xfree@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).