public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jon TURNEY <jon.turney@dronecode.org.uk>
To: cygwin@cygwin.com
Cc: tmacchant@yahoo.co.jp
Subject: Re: xterm fails after update cygwin
Date: Thu, 09 Apr 2015 12:59:00 -0000	[thread overview]
Message-ID: <55267798.4040004@dronecode.org.uk> (raw)
In-Reply-To: <1428540058818-117349.post@n5.nabble.com>

On 09/04/2015 01:40, tmacchant wrote:
>> DISPLAY=:0.0 makes me to see xterm!
>
> Note that so far I can share Cygwin/X for both 32 bit and 64 bit.
> But now it should be started separately
>
> (I am using both 32 bit and 64 bit version because I'm providing cvs
> snapshot of gnuplot on both 32 and 64 bit.)

Because 32-bit and 64-bit cygwin are completely independent, it's not 
possible for a a 32-bit cygwin X client to connect via a unix-domain 
socket to a 64-bit cygwin X server (and vice versa)

So if you want that to work, you will have to use and allow TCP, as 
described in [1]

[1] 
http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-local-noncygwin-clients-cant-connect

-- 
Jon TURNEY
Volunteer Cygwin/X X Server maintainer

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

  reply	other threads:[~2015-04-09 12:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-06  0:13 tmacchant
2015-04-07 23:01 ` tmacchant
2015-04-08 17:13   ` Jon TURNEY
2015-04-09  0:21     ` tmacchant
2015-04-09  0:41       ` tmacchant
2015-04-09 12:59         ` Jon TURNEY [this message]
2015-04-09 13:39           ` tmacchant

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=55267798.4040004@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin@cygwin.com \
    --cc=tmacchant@yahoo.co.jp \
    /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).