From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 36018 invoked by alias); 30 Sep 2015 05:15:17 -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 35963 invoked by uid 89); 30 Sep 2015 05:15:10 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS,URIBL_SBL autolearn=ham version=3.3.2 X-HELO: mail-io0-f172.google.com Received: from mail-io0-f172.google.com (HELO mail-io0-f172.google.com) (209.85.223.172) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Wed, 30 Sep 2015 05:15:08 +0000 Received: by iofh134 with SMTP id h134so35482948iof.0 for ; Tue, 29 Sep 2015 22:15:05 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=b0HJTQtqF+n202C+M6ViQn781NDFrBAeogwXEpQEGDA=; b=ap8v+/O1umA6cTWYyB7wiYOvXKmHrPGTClZd71GfMhjvwJFN5ehYoF+h5PE072MFR5 1Q/eO2EShdOx2X2tDuAnv3+mYd9qxVwWULpY3+PKfjZ1Wqm3Z75x5Qx82zstwOVRQEvv qnFQMeqP8yiSu21V3YhVK5v4aafc21qR/FF0JkETZSE/Hqh2ATsMQrxXq0JD6qhhZ86I TRyCMxISwV63UVDbEnlUoswA0+muezgLAEQIjGWNwLyTM+h3ylYanztxolili0yONgyJ zlL9GGvVhZAdQmxagO8FgxPhdKYaERJl9Xx7IEYrLz7bPdT64lxMBHuEAEIGVsCqWRYh JZAg== X-Gm-Message-State: ALoCoQn5J4Eg9mBanzN+EMVK1yMpPopVKa5ZjXpisl6/lPX5NeaUB32k09okJzyQu9/3JyeL3YqL MIME-Version: 1.0 X-Received: by 10.107.35.20 with SMTP id j20mr2236561ioj.39.1443590104898; Tue, 29 Sep 2015 22:15:04 -0700 (PDT) Received: by 10.36.5.147 with HTTP; Tue, 29 Sep 2015 22:15:04 -0700 (PDT) In-Reply-To: References: Date: Wed, 30 Sep 2015 05:15:00 -0000 Message-ID: Subject: Re: Mintty Crash on Exit after SSH on Windows 10 From: Bryan Tong To: cygwin@cygwin.com Content-Type: text/plain; charset=UTF-8 X-SW-Source: 2015-09/txt/msg00511.txt.bz2 Okay, The plot thickens. After I renamed my home folder so Cygwin would make a new one. The problem seems to be gone. I will continue to test and see if it comes back. Maybe something in my home folder is making it unhappy. On Tue, Sep 29, 2015 at 11:10 PM, Bryan Tong wrote: > I wasnt able to get any of the replies however I saw them on the mailing list. > > First of all, yes the problems continue if I type "exit" into each windows. > > Also happens if I just press the "X" on the window. > > Enter, doesnt do anything on the window. I have to either wait about > 60 seconds for the window to exit after claiming to not respond or I > have to use the task manager to kill it. > > I am trying the others now and will let you know. > > What I can tell you is that I just did a fresh install of cygwin > 32bit. I install nano, vim, ssh, ping as well was the base package > set. > > The problem continues on that installation as well. > > On Thu, Sep 17, 2015 at 2:10 AM, 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. >> >> What makes this issue more interesting is that I cant always reproduce >> it. It only happens after I have long standing SSH sessions. >> >> After I press "CTL + a + d" the final time when I am back at the >> cygwin login prompt. The window hangs and my cursor disappears when I >> try to mouse into the window (this includes the title bar, an exit >> buttons). At this point the only option is killing from the task >> manager or waiting about a minute until the window dies. >> >> I am thinking this has to do with unclosed sockets after I have done a >> bunch of googling on what might be causing this. >> >> There is one mailing thread pertaining to a similar issue but it >> doesnt match up exactly. >> >> It definitely started directly after the upgrade to Windows 10. I did >> not upgrade cygwin until after I ran into this problem. However the >> issue still persists after the upgrade. I believe I am running the >> latest versions. >> >> I have attached my cygcheck to help. >> >> 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 >> >> I can almost always reproduce this after working on remote servers. >> However when I try to do it on command it happen every time. >> >> I want to point out that I am also using this SSH option. >> >> ServerAliveInterval 30 >> >> I am starting to wonder if maybe that option is causing SSH to keep >> the window open as it tries to keep the server alive. It seems that >> the 30 second window is close to how long I am seeing these windows >> hang open. >> >> I am not even sure where to look for more debugging. I am more curious >> if anyone else is experiencing this? >> >> Please note that I upgraded my Desktops from Windows 7 -> Windows 10 >> and they both see the problem. On the other hand my laptop I upgraded >> from Windows 8 -> Windows 10 and it continues to work normally. >> >> Any help would be appreciated I am stumped on this one. >> >> Thanks >> >> -- >> eSited LLC >> (701) 390-9638 > > > > -- > eSited LLC > (701) 390-9638 -- eSited LLC (701) 390-9638 -- 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