public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: Cygwin windows won't close
Date: Wed, 10 Oct 2018 06:37:00 -0000	[thread overview]
Message-ID: <fcd703b4-bccd-4a97-a953-8aec9279fed8@towo.net> (raw)
In-Reply-To: <a8097f95-0221-b726-6631-0cde2e0b02d1@gmail.com>



Am 09.10.2018 um 20:46 schrieb Marco Atzeri:
> Am 09.10.2018 um 19:22 schrieb Ziegelmiller, Lyle(AWF) via cygwin:
>>
>
>>
>> Then I don't see much of the cause for such a behavior from Cygwin side.
>> May be other software interfering. Do you have a particularly zealous 
>> "antivirus", pehaps?
>>
>> We're using "Symantec Endpoint Protection", Version 14.
>>
>> I could see an anti-virus program preventing the execution of a 
>> Cygwin window, but not the closing of one.
>>
>
> I have seen Symantec in the past creating such problems.
> Probably they inject something in the call sequence.
Which brings me to this suggestions: Please try option 
ConfirmExit=false, does the behaviour change?
Thomas

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2018-10-10  6:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-06 17:31 Ziegelmiller, Lyle(AWF) via cygwin
2018-10-07  0:35 ` Andrey Repin
2018-10-08 17:19   ` Ziegelmiller, Lyle(AWF) via cygwin
2018-10-08 18:05     ` Andrey Repin
2018-10-08 21:44       ` Ziegelmiller, Lyle(AWF) via cygwin
2018-10-09 11:50         ` Andrey Repin
2018-10-09 17:22           ` Ziegelmiller, Lyle(AWF) via cygwin
2018-10-09 18:40             ` cyg Simple
2018-10-09 18:46             ` Marco Atzeri
2018-10-10  6:37               ` Thomas Wolff [this message]
2018-10-14  4:37                 ` Thomas Wolff
2019-01-25 21:53                   ` DaRonStein
2019-01-26  2:45                     ` Brian Inglis
2018-10-07 11:49 ` Marco Atzeri

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=fcd703b4-bccd-4a97-a953-8aec9279fed8@towo.net \
    --to=towo@towo.net \
    --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).