From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 81744 invoked by alias); 17 Sep 2015 21:05:20 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 81734 invoked by uid 89); 17 Sep 2015 21:05:20 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=3.8 required=5.0 tests=AWL,BAYES_50,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 X-HELO: mout.kundenserver.de Received: from mout.kundenserver.de (HELO mout.kundenserver.de) (212.227.17.13) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Thu, 17 Sep 2015 21:05:19 +0000 Received: from [192.168.178.27] ([95.90.245.92]) by mrelayeu.kundenserver.de (mreue104) with ESMTPSA (Nemesis) id 0MFKXk-1ZQZQd1ZRc-00EKzJ for ; Thu, 17 Sep 2015 23:05:15 +0200 Subject: Re: Mintty Hang on Exit after SSH on Windows 10 To: cygwin@cygwin.com References: <55FA927F.60704@gmail.com> From: Thomas Wolff Message-ID: <55FB2B0C.9050004@towo.net> Date: Thu, 17 Sep 2015 21:05:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <55FA927F.60704@gmail.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-UI-Out-Filterresults: notjunk:1;V01:K0:BEDHHq8zdeU=:Q3WRm9ImfqBsedfTxmfoZd QVwn6sm/MGcmzPHNaARXGk2BONBOd6/9EOWEN9rFqAJpbzKn2uXW7QItf6G/G+zk9aDwiM2pW aC/oj5jOylsfhYP4t3B4lKworIh8zMQqwZTQ9cJbnTYodsON6Xr7XpAR/HDQ+wNV8WBmFNjPU 2Kwc9CHr3UVpcdcHN8NajRKphYqcCKHDA47/5SsMhFrmCnCMNdE1JoyRpFYglqWrcwJpHCTtm 2s+45khq0j+XDoXWM3nI3Hjdekw5Mrrk5CwSpQ/PtDEiaj3dxxZMhsx0Kp9nWVaSfgy293KOg 0Z+Xzn8uM7jcAHHztyMu1nRCeI3h2YRtYzMvYhJy0OKd86hWykbOOYfLmqmmqxqlGnd0/8AYR ZXnU0OsGd/U0cPazGf6xcT9xbarH1kDcm+YVeJXaYihIkHPwbwUP6F7LNXRQ6ibBkhB/lKP+/ AeoEg5rDCu2ZVtzDqiZQb5XnqzqO+WRlt3TqetL2EHicHjRTR/GICa/trsyeCESkBanFIk/uR 7M7uYKUTi8jcJwYazmkjGAs4/1afcWntnstatANKyDJ5YyJVNku/Y+fwpnWWVvI2JN6HoGT9t SuJ3evocUWGHtkSrXAHBzYfOBgLKXBtsObKHaP5Uh9rmswBZdqlNPqeCWBz+qKutfJSEkXLGG VEVeHkvzqmrHvgvMZyYHg2HAd1wOZpAdbqrUNtVSFN+yniIhJAsJcwiftHLkgW1B7rhd5q0yt CGgQcFL2d7+exXdV X-IsSubscribed: yes X-SW-Source: 2015-09/txt/msg00270.txt.bz2 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