public inbox for
help / color / mirror / Atom feed
From: Fj <>
Subject: Re: Can't open display with PuTTY and xinit 1.3.4-1
Date: Tue, 24 Feb 2015 16:55:00 -0000	[thread overview]
Message-ID: <> (raw)

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.

Hi, I updated Cygwin today and hit the same problem, except even after
I added "-listen tcp" xterm (and gvim) still refused to work
complaining about "No protocol specified" (before was: "Can't open

Putty logs say "Opening X11 forward connection succeeded" (before
"-listen tcp" it was: "Forwarded X11 connection terminated due to
local error"), which seems to indicate that the problem is with the X
server (and the way xterm/gvim communicate with it).

Ssh-ing to the server from Cygwin terminal works and I can even launch
gvim from the Putty's tty by specifying the same DISPLAY the Cygwin
connection provides.

After reverting to some early 2014 version of xinit and xorg (thank
god for Cygwin Time Machine) everything resumed working properly.

(on a side note, I tried to figure out what are the possible "-listen"
options by looking at the xserver code, there are three, "tcp",
"unix", "local". What does "local" mean, couldn't it be loopback
adapter? Where is "_XSERVTransNoListen" function implemented?)



Unsubscribe info:
Problem reports:

             reply	other threads:[~2015-02-24 16:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-24 16:55 Fj [this message]
2015-02-24 21:00 ` Jon TURNEY
  -- strict thread matches above, loose matches on Subject: below --
2015-01-05 11:32 Laurens Blankers
2015-01-05 17:31 ` Yaakov Selkowitz
2015-01-06  9:12   ` Laurens Blankers

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).