From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: Xwin has stopped working
Date: Sat, 12 Dec 2020 11:54:32 -0500 [thread overview]
Message-ID: <04d038c3-82a0-d532-11ed-5a5f0b9bd94f@cornell.edu> (raw)
In-Reply-To: <CAFOXTdeXGzH4sZetr6TrNjGcdJKmQgZ51zBZxO97k9dGr8jXaQ@mail.gmail.com>
On 12/12/2020 11:19 AM, Andrey Voropaev via Cygwin wrote:
> On Sat, Dec 12, 2020 at 11:57 AM Marco Atzeri via Cygwin
> <cygwin@cygwin.com> wrote:
>>
>> On 10.12.2020 14:17, Andrey Voropaev via Cygwin wrote:
>>> 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:
>>
>> Still working on my W10 after Windows update
>>
>> Do you have any .startxwinrc ?
>
> Not really. The file exists and contains call to xrdb, but it was not
> executable,
> so it was not used. When the problem appeared, I've made it executable, but
> it didn't change anything
>>
>> Anything more on the /var/log/xwin/XWin.0.log
>
> Not really. I've attached complete log to this Email.
>
>>
>> Please show the full call to startxwin and provide the full cygcheck.out
>
> I just called startxwin without any arguments. The cygcheck.out is
> also attached.
Your cygcheck output contains the following:
Potential app conflicts:
ZoneAlarm Personal Firewall
Detected: HKLM Registry Key.
Can you try disabling ZoneAlarm and see if that helps?
Ken
next prev parent reply other threads:[~2020-12-12 16:54 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 [this message]
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
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=04d038c3-82a0-d532-11ed-5a5f0b9bd94f@cornell.edu \
--to=kbrown@cornell.edu \
--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).