public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jim Garrison <jhg@jhmg.net>
To: cygwin@cygwin.com
Subject: XWindows curiosity with two cygwin instances
Date: Thu, 21 May 2020 17:28:33 -0700	[thread overview]
Message-ID: <15494797-95f5-c94e-875d-4330da656b21@jhmg.net> (raw)

I have my normal Cygwin+Cygwin/X instance at c:\cygwin64.  I've
temporarily set up another instance (no X) at u:\cygwin64.  I notice
that if I start up the X server on the first instance, X programs
started under the second instance cannot connect to the XServer.
They always get, for example:

jim@HOME10 ~
$ xclock
Error: Can't open display: :0

But this works just fine if I run the same command in a mintty window
launched under the first instance.

This happens even with "Disable access control" set, and also
"xhost +".  I also tried DISPLAY=localhost:0 but that doesn't
work because the X Server isn't listening on port 6000.

Is this an artifact of how Cygwin/X emulates unix sockets?

What option do I need to change to have the XServer listen on
port 6000?

TIA

-- 
Jim Garrison jhg@acm.org

             reply	other threads:[~2020-05-22  0:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-22  0:28 Jim Garrison [this message]
2020-05-22  4:11 ` Jim Garrison

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=15494797-95f5-c94e-875d-4330da656b21@jhmg.net \
    --to=jhg@jhmg.net \
    --cc=cygwin@cygwin.com \
    --cc=jhg@acm.org \
    /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).