From: Steinar Bang <sb@dod.no>
To: cygwin@cygwin.com
Subject: Re: cygwin x11 doesn't start after windows 10 upgrade
Date: Sat, 13 Jun 2020 11:04:13 +0200 [thread overview]
Message-ID: <upzcftaz2v76.fsf@dod.no> (raw)
In-Reply-To: <upzcv9jx3891.fsf@dod.no>
>>>>> Steinar Bang <sb@dod.no>:
> Platform: amd64, windows 10 10.0.18363 Build 18363,
> cygwin xorg-server 1.20.5-3, xlaunch 20160530-1
> I start X11 by double clicking the following config.xlaunch:
> https://gist.github.com/steinarb/8687e2113c601e061da909e75a180f39
> After the reboot caused by a windows 10 upgrade, launching X11 using
> xlaunch have stopped working.
[snip! attempts at fixing]
> Here's XWin.0.log from a startup attempt:
> https://gist.github.com/steinarb/dacfec5172fd547cbec7c87723163193
The log doesn't have any obvious errors, but I've tried googling the
most error-message-like lines (so far without any luck).
I tried googling "xorg.conf is not supported" and found
https://stackoverflow.com/questions/27526938/x-does-not-start-after-cygwin-upgrade
(title was promising but this is from 2014 and probably irrelevant)
I tried googling "Returning, supported engines 00000005" and found
https://sourceware.org/legacy-ml/cygwin/2015-09/msg00084.html
(title also promising, but from 2015 and probably irrelevant as well)
Is the problem that I'm using xlaunch? From the version number it looks
like it is from 2016? Has the world change enough that it now longer
works for launching x?
What does people use to launch cygwin X these days?
next prev parent reply other threads:[~2020-06-13 9:04 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 15:57 Steinar Bang
2020-06-13 6:30 ` Marco Atzeri
2020-06-13 9:30 ` Steinar Bang
2020-06-13 11:22 ` Marco Atzeri
2020-06-13 12:00 ` Steinar Bang
2020-06-13 13:22 ` Marco Atzeri
2020-06-13 15:48 ` Steinar Bang
2020-06-13 16:44 ` Steinar Bang
2020-06-13 20:37 ` Andrey Repin
2020-06-13 9:35 ` Steinar Bang
2020-06-13 9:55 ` Steinar Bang
2020-06-13 11:31 ` Marco Atzeri
2020-06-13 12:03 ` Steinar Bang
2020-06-13 12:09 ` Steinar Bang
2020-06-13 13:14 ` Holger, Vodafone
2020-06-13 13:29 ` Marco Atzeri
2020-06-13 9:04 ` Steinar Bang [this message]
2020-06-13 21:15 ` Jon Turney
2020-06-14 10:44 ` Steinar Bang
2020-06-14 11:18 ` Henry S. Thompson
2020-06-14 16:12 ` Steinar Bang
2020-06-14 17:49 ` Marco Atzeri
2020-06-14 21:45 ` Steinar Bang
2020-06-14 22:21 ` Holger, Vodafone
2020-06-15 12:17 ` Holger, Vodafone
2020-06-15 12:57 ` Holger, Vodafone
2020-06-16 4:22 ` Brian Inglis
2020-08-02 20:25 ` Steinar Bang
2020-08-02 21:00 ` Eliot Moss
2020-08-04 12:01 ` Steinar Bang
2020-08-04 13:12 ` Hamish McIntyre-Bhatty
2020-08-04 16:55 ` ASSI
2020-06-16 4:59 ` ASSI
2020-07-02 15:01 ` Steinar Bang
2020-07-02 22:12 ` Holger, Vodafone
2020-06-16 11:46 ` Holger, Vodafone
2020-06-26 9:15 ` Holger, Vodafone
2020-07-02 14:42 ` Steinar Bang
2020-06-14 6:18 ` Marco Atzeri
2020-06-14 10:38 ` Steinar Bang
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=upzcftaz2v76.fsf@dod.no \
--to=sb@dod.no \
--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).