public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Michael DePaulo <mikedep333@gmail.com>
To: cygwin-xfree@cygwin.com
Cc: Fergus Daly <fergusd@frontier-science.co.uk>
Subject: Re: Following update to XWin or xorg-server: changed syntax to get a xterm terminal window
Date: Wed, 10 Jun 2015 11:37:00 -0000	[thread overview]
Message-ID: <CAMKht8jui05HnCu4a4vYXRo9by=hjH518BoMBmxrprvBAnAfhA@mail.gmail.com> (raw)
In-Reply-To: <9D9AC45310887B40A7245734E850FBE1256D1D45@FS-MX02.frontier.local>

On Wed, Jun 10, 2015 at 7:28 AM, Fergus Daly
<fergusd@frontier-science.co.uk> wrote:
> For ages I used
>     XWin -nolock -nolisten local -multiwindow &
>     xterm -display localhost:0.0
> to get a xterm terminal.
> Following recent updates I get a fatal error: "Cannot establish any listening sockets."
> In the past, updates to XWin have sometimes led to similar difficulties, but I have always managed to iterate to a new successful joint syntax
>     XWin <arguments>
>     xterm <arguments>
> but this time I am totally stymied.
> Can anybody offer me a working syntax please?
> Thank you.
> Fergus

By default, XWin 1.17 no longer listens on TCP sockets, only on unix
domain sockets.
https://www.cygwin.com/ml/cygwin-announce/2015-06/msg00003.html

However, "-nolisten local" disables unix domain sockets.,

So to use unix domain sockets:
    XWin -nolock -multiwindow &
    xterm -display :0.0

Or to keep using TCP sockets:
    XWin -nolock -nolisten local -listen tcp -multiwindow &
    xterm -display localhost:0.0

-Mike

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


  reply	other threads:[~2015-06-10 11:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-10 11:29 Fergus Daly
2015-06-10 11:37 ` Michael DePaulo [this message]
2015-09-17  3:11   ` Paul

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='CAMKht8jui05HnCu4a4vYXRo9by=hjH518BoMBmxrprvBAnAfhA@mail.gmail.com' \
    --to=mikedep333@gmail.com \
    --cc=cygwin-xfree@cygwin.com \
    --cc=fergusd@frontier-science.co.uk \
    /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).