From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Cygwin/X fatal error
Date: Sat, 8 Jan 2022 09:35:41 +0100 [thread overview]
Message-ID: <47ce1f07-5c6a-3386-04b1-e1abb8784c9f@gmail.com> (raw)
In-Reply-To: <DB6P18901MB005546D4E988D9959CCABC86A44E9@DB6P18901MB0055.EURP189.PROD.OUTLOOK.COM>
On 08.01.2022 07:57, Fergus Daly wrote:
> Not quite sure what recent update has caused this failure.
> Up to now (and for a very long time indeed) typing
> $ /bin/xinit /bin/xterm -- -nolock -multiwindow
> at the mintty prompt has successfully started an xterm process.
> Now I get:
> "A fatal error has occurred and Cygwin/X will now exit.
> Cannot establish any listening sockets."
> Over the years the one-liner typed above has had to evolve with changing execs so I'm not surprised, or bothered, at this glitch.
> But can anybody please advise the necessary change in syntax that will again enable a successful xterm from mintty?
> Thank you!
>
Hi Fergus,
It works for me, so it seems not due to the sintax
Can you start X with startxwin ?
Please provide the cygcheck.out as mentioned on
Problem reports: https://cygwin.com/problems.html
Regards
Marco
next prev parent reply other threads:[~2022-01-08 8:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-08 6:57 Fergus Daly
2022-01-08 8:35 ` Marco Atzeri [this message]
2022-01-08 10:55 ` Fergus Daly
2022-01-10 16:04 ` Massimiliano Alvioli
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=47ce1f07-5c6a-3386-04b1-e1abb8784c9f@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@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).