From: <briand@pounceofcats.com>
To: Marco Atzeri via Cygwin <cygwin@cygwin.com>
Subject: Re: Xwin has stopped working
Date: Sat, 12 Dec 2020 13:07:52 -0800 [thread overview]
Message-ID: <20201212130752.5d11367b@quarternote> (raw)
In-Reply-To: <fef2a3bb-345e-eac0-08e5-bacb204f154e@gmail.com>
On Sat, 12 Dec 2020 11:55:07 +0100
Marco Atzeri via Cygwin <cygwin@cygwin.com> wrote:
> On 10.12.2020 14:17, Andrey Voropaev via Cygwin wrote:
> > Hello,
> >
> > I was using startxwin to run Xorg in multiwindow mode. Untill today it
> > worked perfectly. Now my Windows 10 got some updates and Xorg stopped
> > working. I see only following messages at the end of startup:
> >
This is interesting. Just recently my work laptop also went through a windows update and then came down with the X-windows stopped working problem.
I kept running it using either startx AND the xfce session from the windows Cygwin-X menu choicres, and i would get the X-windows screen and then nothing would happen, i.e. i would get no terminal or the proper background color. I did this several times with reboots in-between.
I then went to the cygwin-X menu and ran the first thing on the menu,and it worked...
I can't remember which menu choice that is, I'll look it up and report back.
Unsure if that's a coincidence or not, but it's awfully strange that i tried the usual "startx" and even XFCE session in the windows menu several times each, between reboots and nothing worked.
But the first time I selected that first menu item from the Cygwin-X menu choices it worked.
That's not the first time this happened to me, although I'm not sure if it has always correlated with a windows upgrades but in this particular instance it definitely did.
prev parent reply other threads:[~2020-12-12 21:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-10 13:17 Andrey Voropaev
2020-12-12 10:55 ` Marco Atzeri
2020-12-12 16:19 ` Andrey Voropaev
2020-12-12 16:54 ` Ken Brown
2020-12-13 8:10 ` Andrey Voropaev
2020-12-14 13:59 ` Ken Brown
2020-12-14 16:50 ` Andrey Voropaev
2020-12-12 21:07 ` briand [this message]
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=20201212130752.5d11367b@quarternote \
--to=briand@pounceofcats.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).