public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: "J. Offerman" <jofferman@gmail.com>
To: cygwin-xfree <cygwin-xfree@cygwin.com>
Subject: Re: remote xterm's can't open display after upgrade
Date: Fri, 12 Dec 2014 22:03:00 -0000	[thread overview]
Message-ID: <CA+2me80A3a60RMGx0arriqWcqeh6+oiz_YKbSvByYPetSqyydw@mail.gmail.com> (raw)
In-Reply-To: <5489ED06.5040606@dronecode.org.uk>

Instead of bothering with the nolisten option and running

$ ssh centos6

Just do this:

$ ssh -Y centos6

without touching the xserver option. That's what Jon meant. I also
stumbled upon this awhile back and pulled my hair(from whereever I
still got them).


On Thu, Dec 11, 2014 at 11:14 AM, Jon TURNEY
<jon.turney@dronecode.org.uk> wrote:
> On 11/12/2014 18:31, Don Webster wrote:
>>
>> I needed to upgrade gs to gs 9.15, so I ran setup yesterday. It
>> wanted to update a whole bunch of stuff, including X. OK, fine, I
>> hadn't updated cygwin in quite a while, and I had other stuff to do.
>>
>> After the upgrade, I can't display remote xterms. OK, my old X
>> shortcut didn't work, but I found "XWin Server" and pinned it to my
>> task bar. I launch that and I have the X server running, and a local
>> xterm pops up. I ssh into my linux server, and run my xterm, and get
>> "can't open display". I did these steps.
>>
>> - turned off my Windows Firewall (I am on a safe, local network). -
>> launched XWin Server.
>>
>> In the xterm that popped up:
>> dcw@dcwdt02 ~
>> $ xhost +
>> access control disabled, clients can connect from any host
>>
>> dcw@dcwdt02 ~
>> $ ssh centos6
>> Last login: Wed Dec 10 16:31:16 2014 from dcwdt02
>> centos6% setenv DISPLAY 10.11.22.33:0.0    # I use tcsh
>> centos6% xterm
>> xterm Xt error: Can't open display: 10.11.22.33:0.0
>> centos6%
>>
>> Is there something obvious?
>
>
> https://cygwin.com/ml/cygwin-xfree/2014-11/msg00029.html
>
> The relevant part is "startx and startxwin now pass '-nolisten tcp' to the
> server by default, which increases security in the X server by not opening a
> port to TCP connections. The '-listen' flag can be passed as a server
> argument to override this."
>
> Your choices are to add the '-listen' flag to the startxwin invocation, or
> (better) to use 'ssh -Y' and not explicitly set DISPLAY (See
> http://x.cygwin.com/docs/ug/using-remote-apps.html#using-remote-apps-ssh)
>
> --
> Jon TURNEY
> Volunteer Cygwin/X X Server maintainer
>
> --
> 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/
>

--
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/


  parent reply	other threads:[~2014-12-12 22:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-11 18:31 Don Webster
2014-12-11 19:14 ` Jon TURNEY
2014-12-11 21:16   ` Don Webster
2014-12-12 22:03   ` J. Offerman [this message]
2014-12-12 19:55 ` JimE
2014-12-14 22:43   ` Linda Walsh

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=CA+2me80A3a60RMGx0arriqWcqeh6+oiz_YKbSvByYPetSqyydw@mail.gmail.com \
    --to=jofferman@gmail.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).