From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: Mintty Hang on Exit after SSH on Windows 10
Date: Thu, 17 Sep 2015 21:05:00 -0000 [thread overview]
Message-ID: <55FB2B0C.9050004@towo.net> (raw)
In-Reply-To: <55FA927F.60704@gmail.com>
Am 17.09.2015 um 12:14 schrieb Marco Atzeri:
> On 17/09/2015 10:10, Bryan Tong wrote:
>> Hello,
>>
>> I recently upgraded to Windows 10 and ever since I have I am getting a
>> hang every time I try to exit a Mintty window after using SSH.
First: a hang is not a crash.
>>
>> What makes this issue more interesting is that I cant always reproduce
>> it. It only happens after I have long standing SSH sessions.
>>
>
>> Best way to reproduce
>>
>> 1) Open mintty
>> 2) ssh to a host
>> 3) idle on this host for say 5 minutes
>> 4) press "ctl + a + d" to disconnect from the host
>> 5) press "ctl + a + d" to disconnect from the Mintty window
>
> what happens if you type "exit" instead of "ctl + a + d" ?
What is ctl+a+d anyway? Both ctrl+a and ctrl+d in sequence?
>
>> I can almost always reproduce this after working on remote servers.
>> However when I try to do it on command it happen every time.
You may have configured hold mode "error" (e.g. Hold=error in
$HOME/.minttry).
Does the terminal close when you type Enter in it?
Otherwise, and in any case, please test also with Cygwin console or/and
xterm. Many problems in interactive response reported with mintty turn
out to actually have some other context.
------
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
next prev parent reply other threads:[~2015-09-17 21:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-17 8:10 Mintty Crash " Bryan Tong
2015-09-17 10:14 ` Marco Atzeri
2015-09-17 21:05 ` Thomas Wolff [this message]
2015-09-17 21:36 ` Mintty Hang " Warren Young
2015-09-30 5:10 ` Mintty Crash " Bryan Tong
2015-09-30 5:15 ` Bryan Tong
2015-09-30 5:21 ` Bryan Tong
2015-11-21 1:19 ` Bryan Tong
2017-11-03 20:02 ` Rick Maus
2018-04-23 15:48 ` cyg
2018-04-23 17:38 ` Thomas Wolff
2015-09-30 8:54 ` Thomas Wolff
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=55FB2B0C.9050004@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).