X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=rpmS3q/7913fNjvX
	ilfAZjJ2Q5PMuMuIbmtIHtD7mjro9oeQGCjYoxHkUBN/5YIwXp6k8xiz7gyhth6x
	71yE3s3AQFtZv4lnGwqmk+JwVQ7NJ3t2LJuLgTbepfZ2MCakVhtp1u/A4K2cYGTo
	XJTR010FJFsM0Zldm8zeUErbnkE=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; s=default; bh=EaWcIQLHThXdiZck8B7i2S
	xmpFA=; b=IPhDbvOTU7rxbFs3urce0CxRcEv1p9FjdOXVNqRZuk2uHyMvUd4ByD
	Ccfs4Iz1XOeV+0LJB/QgqdtGx0Ybx3dO2mdsc0Nd9/APcAGuXPIQ4+0wo7bWabrw
	rVUxZKJO2g+fB5kwA3OOjx1aR5/aw7OMpzjmH7S2AHRuwdJyZrFy0=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=0.8 required=5.0 tests=AWL,BAYES_05,FREEMAIL_FROM,KAM_THEBAT,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=no version=3.3.2 spammy=Enter, HAuthentication-Results:header.i, H*R:D*cygwin.com, H*RU:192.168.1.10
X-HELO: forward5m.cmail.yandex.net
Authentication-Results: smtp2m.mail.yandex.net; dkim=pass header.i=@yandex.ru
X-Yandex-Suid-Status: 1 0,1 0
Date: Wed, 24 May 2017 13:05:47 +0300
From: Andrey Repin <anrdaemon AT yandex DOT ru>
Reply-To: cygwin AT cygwin DOT com
Message-ID: <498347636.20170524130547@yandex.ru>
To: Dani Moncayo <dmoncayo AT gmail DOT com>, cygwin AT cygwin DOT com
Subject: Re: Mintty does not close after "exit" command
In-Reply-To: <CAH8Pv0iiRvbGcd1_BYTXT+jRmUs_oYMLezVqT5Q6iFN-1QeL4g@mail.gmail.com>
References: <CAH8Pv0iiRvbGcd1_BYTXT+jRmUs_oYMLezVqT5Q6iFN-1QeL4g AT mail DOT gmail DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

Greetings, Dani Moncayo!

> Hi,

> subject line says it all.

> I've been experiencing this problem for some months, on windows 10.
> But the problem does not appear in another windows 8.1 system I use.

> To reproduce the problem, just open the standard cygwin terminal (e.g.
> by double-clicking the desktop icon), an then type the "exit" command
> in the bash shell.

> I see a "logout" message for a fraction of a second, then the terminal
> becomes empty (without text), but the mintty window remains visible
> but unresponsive, with the title bar showing "~ (Not Responding)".

Anything suspicious in logout script?
One known cause if it could be reproduced fairly easy with ssh to a remote
host. Once ssh session ends, MinTTY will stick after exit, until you press
Enter.


-- 
With best regards,
Andrey Repin
Wednesday, May 24, 2017 13:04:08

Sorry for my terrible english...


--
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