From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: Xwin has stopped working
Date: Mon, 14 Dec 2020 08:59:52 -0500 [thread overview]
Message-ID: <e5ed1790-bcf5-6048-f8ee-5d9ae41fa576@cornell.edu> (raw)
In-Reply-To: <CAFOXTddwxWo5Bh6NAw9zNdm0LgvFeJNSephF5dgxY3Z3xQ7njQ@mail.gmail.com>
On 12/13/2020 3:10 AM, Andrey Voropaev via Cygwin wrote:
> On Sat, Dec 12, 2020 at 5:56 PM Ken Brown via Cygwin <cygwin@cygwin.com> wrote:
>>
>> 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:
>>
>> 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?
>
> Not really, this is company-laptop, so I don't have Admin-password.
> Well, I guess our company has made everything possible to render
> laptops useless.
>
> Any way to work around it?
Not that I know of. But we don't even know yet that ZoneAlarm is the issue.
Could you get your admin to temporarily disable it for testing, or perhaps to
exclude the Cygwin directory?
Ken
next prev parent reply other threads:[~2020-12-14 13:59 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 [this message]
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=e5ed1790-bcf5-6048-f8ee-5d9ae41fa576@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).