* Mintty Crash on Exit after SSH on Windows 10
@ 2015-09-17 8:10 Bryan Tong
2015-09-17 10:14 ` Marco Atzeri
2015-09-30 5:10 ` Mintty Crash " Bryan Tong
0 siblings, 2 replies; 12+ messages in thread
From: Bryan Tong @ 2015-09-17 8:10 UTC (permalink / raw)
To: cygwin
[-- Attachment #1: Type: text/plain, Size: 2118 bytes --]
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
[-- Attachment #2: cygcheck.out --]
[-- Type: application/octet-stream, Size: 23541 bytes --]
Cygwin Configuration Diagnostics
Current System Time: Thu Sep 17 08:57:04 2015
Windows 7 Professional Ver 6.1 Build 7600
Path: C:\cygwin64\usr\local\bin
C:\cygwin64\bin
C:\Program Files (x86)\PHP
C:\program files (x86)\amd app\bin\x86_64
C:\program files (x86)\amd app\bin\x86
C:\programdata\oracle\java\javapath
C:\windows\system32
C:\windows
C:\windows\system32\wbem
C:\windows\system32\windowspowershell\v1.0
C:\program files (x86)\ati technologies\ati.ace\core-static
C:\program files (x86)\git\cmd
C:\program files (x86)\git\bin
C:\program files\microsoft sql server\110\tools\binn
C:\program files (x86)\microsoft sdks\typescript\1.0
C:\nodist\bin
C:\ffmpeg\bin
C:\python27
C:\mongodb\bin
C:\mp4box
C:\python27\scripts
C:\bin
C:\program files (x86)\mysql\mysql utilities 1.4
C:\program files (x86)\mysql\mysql utilities 1.4\doctrine extensions for php
C:\nginx
C:\program files (x86)\skype\phone
C:\Program Files (x86)\AMD\ATI.ACE\Core-Static
C:\WINDOWS\system32
C:\WINDOWS
C:\WINDOWS\System32\Wbem
C:\WINDOWS\System32\WindowsPowerShell\v1.0
C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static
C:\Program Files\Git\cmd
C:\Program Files\Git\mingw64\bin
C:\Program Files\Git\usr\bin
Output from C:\cygwin64\bin\id.exe
UID: 1000(Mac) GID: 513(None)
513(None) 559(Performance Log Users)
545(Users)
SysDir: C:\WINDOWS\system32
WinDir: C:\WINDOWS
USER = 'Mac'
PWD = '/home/Mac'
HOME = '/home/Mac'
USERDOMAIN_ROAMINGPROFILE = 'Mac-PC'
HOMEPATH = '\Users\Mac'
APPDATA = 'C:\Users\Mac\AppData\Roaming'
ProgramW6432 = 'C:\Program Files'
HOSTNAME = 'Mac-PC'
SHELL = '/bin/bash'
TERM = 'xterm'
PROCESSOR_IDENTIFIER = 'AMD64 Family 21 Model 2 Stepping 0, AuthenticAMD'
PROFILEREAD = 'true'
WINDIR = 'C:\WINDOWS'
PUBLIC = 'C:\Users\Public'
OLDPWD = '/cygdrive/c/WINDOWS/System32'
ORIGINAL_PATH = '/cygdrive/c/Program Files (x86)/PHP:/cygdrive/c/program files (x86)/amd app/bin/x86_64:/cygdrive/c/program files (x86)/amd app/bin/x86:/cygdrive/c/programdata/oracle/java/javapath:/cygdrive/c/windows/system32:/cygdrive/c/windows:/cygdrive/c/windows/system32/wbem:/cygdrive/c/windows/system32/windowspowershell/v1.0:/cygdrive/c/program files (x86)/ati technologies/ati.ace/core-static:/cygdrive/c/program files (x86)/git/cmd:/cygdrive/c/program files (x86)/git/bin:/cygdrive/c/program files/microsoft sql server/110/tools/binn:/cygdrive/c/program files (x86)/microsoft sdks/typescript/1.0:/cygdrive/c/nodist/bin:/cygdrive/c/ffmpeg/bin:/cygdrive/c/python27:/cygdrive/c/mongodb/bin:/cygdrive/c/mp4box:/cygdrive/c/python27/scripts:/cygdrive/c/bin:/cygdrive/c/program files (x86)/mysql/mysql utilities 1.4:/cygdrive/c/program files (x86)/mysql/mysql utilities 1.4/doctrine extensions for php:/cygdrive/c/nginx:/cygdrive/c/program files (x86)/skype/phone:/cygdrive/c/Program Files (x86)/AMD/ATI.ACE/Core-Static:/cygdrive/c/WINDOWS/system32:/cygdrive/c/WINDOWS:/cygdrive/c/WINDOWS/System32/Wbem:/cygdrive/c/WINDOWS/System32/WindowsPowerShell/v1.0:/cygdrive/c/Program Files (x86)/ATI Technologies/ATI.ACE/Core-Static:/cygdrive/c/Program Files/Git/cmd:/cygdrive/c/Program Files/Git/mingw64/bin:/cygdrive/c/Program Files/Git/usr/bin'
USERDOMAIN = 'Mac-PC'
PHPRC = 'C:\Program Files (x86)\PHP\'
CommonProgramFiles(x86) = 'C:\Program Files (x86)\Common Files'
OS = 'Windows_NT'
FPS_BROWSER_APP_PROFILE_STRING = 'Internet Explorer'
ALLUSERSPROFILE = 'C:\ProgramData'
windows_tracing_flags = '3'
windows_tracing_logfile = 'C:\BVTBin\Tests\installpackage\csilogfile.log'
!:: = '::\'
TEMP = '/tmp'
COMMONPROGRAMFILES = 'C:\Program Files\Common Files'
USERNAME = 'Mac'
PROCESSOR_LEVEL = '21'
ProgramFiles(x86) = 'C:\Program Files (x86)'
PSModulePath = 'C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules\'
FP_NO_HOST_CHECK = 'NO'
SYSTEMDRIVE = 'C:'
AMDAPPSDKROOT = 'C:\Program Files (x86)\AMD APP\'
__COMPAT_LAYER = 'Win7RTM DetectorsWin7'
LANG = 'en_US.UTF-8'
VS120COMNTOOLS = 'C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\Tools\'
USERPROFILE = 'C:\Users\Mac'
TZ = 'America/Denver'
PS1 = '\[\e]0;\w\a\]\n\[\e[32m\]\u@\h \[\e[33m\]\w\[\e[0m\]\n\$ '
LOGONSERVER = '\\MAC-PC'
CommonProgramW6432 = 'C:\Program Files\Common Files'
PROCESSOR_ARCHITECTURE = 'AMD64'
LOCALAPPDATA = 'C:\Users\Mac\AppData\Local'
ProgramData = 'C:\ProgramData'
EXECIGNORE = '*.dll'
SHLVL = '1'
PATHEXT = '.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC;.PY'
HOMEDRIVE = 'C:'
COMSPEC = 'C:\WINDOWS\system32\cmd.exe'
TMP = '/tmp'
SYSTEMROOT = 'C:\WINDOWS'
PRINTER = 'Send To OneNote 2013'
PROCESSOR_REVISION = '0200'
NODIST_PREFIX = '\nodist'
FPS_BROWSER_USER_PROFILE_STRING = 'Default'
INFOPATH = '/usr/local/info:/usr/share/info:/usr/info'
PROGRAMFILES = 'C:\Program Files'
NUMBER_OF_PROCESSORS = '8'
SESSIONNAME = 'Console'
COMPUTERNAME = 'MAC-PC'
_ = '/usr/bin/cygcheck'
HKEY_CURRENT_USER\SOFTWARE\Cygwin
HKEY_CURRENT_USER\SOFTWARE\Cygwin\Installations
(default) = '\??\C:\cygwin64'
HKEY_CURRENT_USER\SOFTWARE\Cygwin\Program Options
HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin
HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\Installations
(default) = '\??\C:\cygwin64'
HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\Program Options
HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\setup
(default) = 'C:\cygwin64'
obcaseinsensitive set to 1
Cygwin installations found in the registry:
System: Key: e022582115c10879 Path: C:\cygwin64
User: Key: e022582115c10879 Path: C:\cygwin64
c: hd NTFS 457309Mb 43% CP CS UN PA FC
d: hd NTFS 953739Mb 16% CP CS UN PA FC Data
C:\cygwin64 / system binary,auto
C:\cygwin64\bin /usr/bin system binary,auto
C:\cygwin64\lib /usr/lib system binary,auto
cygdrive prefix /cygdrive user binary,posix=0,auto
Found: C:\cygwin64\bin\awk
Found: C:\Program Files\Git\usr\bin\awk.exe
Warning: C:\cygwin64\bin\awk hides C:\Program Files\Git\usr\bin\awk.exe
-> C:\cygwin64\bin\gawk.exe
Found: C:\cygwin64\bin\bash.exe
Found: C:\Program Files\Git\usr\bin\bash.exe
Warning: C:\cygwin64\bin\bash.exe hides C:\Program Files\Git\usr\bin\bash.exe
Found: C:\cygwin64\bin\cat.exe
Found: C:\Program Files\Git\usr\bin\cat.exe
Warning: C:\cygwin64\bin\cat.exe hides C:\Program Files\Git\usr\bin\cat.exe
Found: C:\cygwin64\bin\cp.exe
Found: C:\Program Files\Git\usr\bin\cp.exe
Warning: C:\cygwin64\bin\cp.exe hides C:\Program Files\Git\usr\bin\cp.exe
Not Found: cpp (good!)
Not Found: crontab
Found: C:\cygwin64\bin\find.exe
Found: C:\windows\system32\find.exe
Warning: C:\cygwin64\bin\find.exe hides C:\windows\system32\find.exe
Found: C:\WINDOWS\system32\find.exe
Warning: C:\cygwin64\bin\find.exe hides C:\WINDOWS\system32\find.exe
Found: C:\Program Files\Git\usr\bin\find.exe
Warning: C:\cygwin64\bin\find.exe hides C:\Program Files\Git\usr\bin\find.exe
Not Found: gcc
Not Found: gdb
Found: C:\cygwin64\bin\grep.exe
Found: C:\Program Files\Git\usr\bin\grep.exe
Warning: C:\cygwin64\bin\grep.exe hides C:\Program Files\Git\usr\bin\grep.exe
Found: C:\cygwin64\bin\kill.exe
Found: C:\Program Files\Git\usr\bin\kill.exe
Warning: C:\cygwin64\bin\kill.exe hides C:\Program Files\Git\usr\bin\kill.exe
Found: C:\cygwin64\bin\ld.exe
Found: C:\cygwin64\bin\ls.exe
Found: C:\Program Files\Git\usr\bin\ls.exe
Warning: C:\cygwin64\bin\ls.exe hides C:\Program Files\Git\usr\bin\ls.exe
Found: C:\cygwin64\bin\make.exe
Found: C:\cygwin64\bin\mv.exe
Found: C:\Program Files\Git\usr\bin\mv.exe
Warning: C:\cygwin64\bin\mv.exe hides C:\Program Files\Git\usr\bin\mv.exe
Not Found: patch
Found: C:\cygwin64\bin\perl.exe
Found: C:\Program Files\Git\usr\bin\perl.exe
Warning: C:\cygwin64\bin\perl.exe hides C:\Program Files\Git\usr\bin\perl.exe
Found: C:\cygwin64\bin\rm.exe
Found: C:\Program Files\Git\usr\bin\rm.exe
Warning: C:\cygwin64\bin\rm.exe hides C:\Program Files\Git\usr\bin\rm.exe
Found: C:\cygwin64\bin\sed.exe
Found: C:\Program Files\Git\usr\bin\sed.exe
Warning: C:\cygwin64\bin\sed.exe hides C:\Program Files\Git\usr\bin\sed.exe
Found: C:\cygwin64\bin\ssh.exe
Found: C:\Program Files\Git\usr\bin\ssh.exe
Warning: C:\cygwin64\bin\ssh.exe hides C:\Program Files\Git\usr\bin\ssh.exe
Found: C:\cygwin64\bin\sh.exe
Found: C:\Program Files\Git\usr\bin\sh.exe
Warning: C:\cygwin64\bin\sh.exe hides C:\Program Files\Git\usr\bin\sh.exe
Found: C:\cygwin64\bin\tar.exe
Found: C:\Program Files\Git\usr\bin\tar.exe
Warning: C:\cygwin64\bin\tar.exe hides C:\Program Files\Git\usr\bin\tar.exe
Found: C:\cygwin64\bin\test.exe
Found: C:\Program Files\Git\usr\bin\test.exe
Warning: C:\cygwin64\bin\test.exe hides C:\Program Files\Git\usr\bin\test.exe
Found: C:\cygwin64\bin\vi.exe
Found: C:\Program Files\Git\usr\bin\vi
Warning: C:\cygwin64\bin\vi.exe hides C:\Program Files\Git\usr\bin\vi
Found: C:\cygwin64\bin\vim.exe
Found: C:\Program Files\Git\usr\bin\vim.exe
Warning: C:\cygwin64\bin\vim.exe hides C:\Program Files\Git\usr\bin\vim.exe
38k 2013/07/19 C:\cygwin64\bin\cygargp-0.dll - os=4.0 img=0.0 sys=5.2
"cygargp-0.dll" v0.0 ts=2013-07-19 15:07
16k 2013/03/26 C:\cygwin64\bin\cygattr-1.dll - os=4.0 img=0.0 sys=5.2
"cygattr-1.dll" v0.0 ts=2013-03-26 18:26
172k 2014/07/09 C:\cygwin64\bin\cygblkid-1.dll - os=4.0 img=0.0 sys=5.2
"cygblkid-1.dll" v0.0 ts=1970-01-01 00:00
64k 2013/03/07 C:\cygwin64\bin\cygbz2-1.dll - os=4.0 img=0.0 sys=5.2
"cygbz2-1.dll" v0.0 ts=2013-03-07 02:54
12k 2014/06/09 C:\cygwin64\bin\cygcom_err-2.dll - os=4.0 img=0.0 sys=5.2
"cygcom_err-2.dll" v0.0 ts=1970-01-01 00:00
9k 2013/03/07 C:\cygwin64\bin\cygcrypt-0.dll - os=4.0 img=0.0 sys=5.2
"cygcrypt-0.dll" v0.0 ts=2013-03-07 09:29
1749k 2014/08/07 C:\cygwin64\bin\cygcrypto-1.0.0.dll - os=4.0 img=0.0 sys=5.2
"cygcrypto-1.0.0.dll" v0.0 ts=1970-01-01 00:00
414k 2014/09/23 C:\cygwin64\bin\cygcurl-4.dll - os=4.0 img=0.0 sys=5.2
"cygcurl-4.dll" v0.0 ts=2014-09-23 20:46
1526k 2013/03/08 C:\cygwin64\bin\cygdb-5.3.dll - os=4.0 img=0.0 sys=5.2
"cygdb-5.3.dll" v0.0 ts=2013-03-08 07:55
111k 2013/03/08 C:\cygwin64\bin\cygdb_cxx-5.3.dll - os=4.0 img=0.0 sys=5.2
"cygdb_cxx-5.3.dll" v0.0 ts=2013-03-08 07:56
472k 2013/03/08 C:\cygwin64\bin\cygdb_sql-5.3.dll - os=4.0 img=0.0 sys=5.2
"cygdb_sql-5.3.dll" v0.0 ts=2013-03-08 07:58
154k 2013/10/20 C:\cygwin64\bin\cygedit-0.dll - os=4.0 img=0.0 sys=5.2
"cygedit-0.dll" v0.0 ts=2013-10-20 21:56
147k 2013/07/31 C:\cygwin64\bin\cygexpat-1.dll - os=4.0 img=0.0 sys=5.2
"cygexpat-1.dll" v0.0 ts=2013-07-31 22:53
22k 2013/05/12 C:\cygwin64\bin\cygffi-6.dll - os=4.0 img=0.0 sys=5.2
"cygffi-6.dll" v0.0 ts=2013-05-12 22:53
56k 2014/05/26 C:\cygwin64\bin\cygformw-10.dll - os=4.0 img=0.0 sys=5.2
"cygformw-10.dll" v0.0 ts=1970-01-01 00:00
68k 2014/08/16 C:\cygwin64\bin\cyggcc_s-seh-1.dll - os=4.0 img=0.0 sys=5.2
"cyggcc_s-seh-1.dll" v0.0 ts=2014-08-15 20:40
40k 2014/05/27 C:\cygwin64\bin\cyggdbm-4.dll - os=4.0 img=0.0 sys=5.2
"cyggdbm-4.dll" v0.0 ts=1970-01-01 00:00
13k 2014/05/27 C:\cygwin64\bin\cyggdbm_compat-4.dll - os=4.0 img=0.0 sys=5.2
"cyggdbm_compat-4.dll" v0.0 ts=1970-01-01 00:00
516k 2014/04/05 C:\cygwin64\bin\cyggmp-10.dll - os=4.0 img=0.0 sys=5.2
"cyggmp-10.dll" v0.0 ts=1970-01-01 00:00
253k 2014/09/19 C:\cygwin64\bin\cyggssapi_krb5-2.dll - os=4.0 img=0.0 sys=5.2
"cyggssapi_krb5-2.dll" v0.0 ts=2014-09-19 18:42
29k 2013/03/14 C:\cygwin64\bin\cyghistory7.dll - os=4.0 img=0.0 sys=5.2
"cyghistory7.dll" v0.0 ts=2013-03-14 11:14
998k 2013/03/07 C:\cygwin64\bin\cygiconv-2.dll - os=4.0 img=0.0 sys=5.2
"cygiconv-2.dll" v0.0 ts=2013-03-07 03:03
195k 2013/04/05 C:\cygwin64\bin\cygidn-11.dll - os=4.0 img=0.0 sys=5.2
"cygidn-11.dll" v0.0 ts=2013-04-05 09:58
38k 2014/06/16 C:\cygwin64\bin\cygintl-8.dll - os=4.0 img=0.0 sys=5.2
"cygintl-8.dll" v0.0 ts=1970-01-01 00:00
179k 2014/09/19 C:\cygwin64\bin\cygk5crypto-3.dll - os=4.0 img=0.0 sys=5.2
"cygk5crypto-3.dll" v0.0 ts=2014-09-19 18:41
701k 2014/09/19 C:\cygwin64\bin\cygkrb5-3.dll - os=4.0 img=0.0 sys=5.2
"cygkrb5-3.dll" v0.0 ts=2014-09-19 18:42
35k 2014/09/19 C:\cygwin64\bin\cygkrb5support-0.dll - os=4.0 img=0.0 sys=5.2
"cygkrb5support-0.dll" v0.0 ts=2014-09-19 18:41
44k 2013/06/18 C:\cygwin64\bin\cyglber-2-4-2.dll - os=4.0 img=0.0 sys=5.2
"cyglber-2-4-2.dll" v0.0 ts=2013-06-17 21:00
243k 2013/06/18 C:\cygwin64\bin\cygldap-2-4-2.dll - os=4.0 img=0.0 sys=5.2
"cygldap-2-4-2.dll" v0.0 ts=2013-06-17 21:00
260k 2013/06/18 C:\cygwin64\bin\cygldap_r-2-4-2.dll - os=4.0 img=0.0 sys=5.2
"cygldap_r-2-4-2.dll" v0.0 ts=2013-06-17 21:01
6k 2014/08/13 C:\cygwin64\bin\cyglsa64.dll - os=4.0 img=0.0 sys=5.2
"cyglsa64.dll" v0.0 ts=2014-08-13 22:05
129k 2014/05/29 C:\cygwin64\bin\cyglzma-5.dll - os=4.0 img=0.0 sys=5.2
"cyglzma-5.dll" v0.0 ts=1970-01-01 00:00
106k 2014/07/01 C:\cygwin64\bin\cygmagic-1.dll - os=4.0 img=0.0 sys=5.2
"cygmagic-1.dll" v0.0 ts=1970-01-01 00:00
158k 2014/08/12 C:\cygwin64\bin\cygman-2-6-7.dll - os=4.0 img=0.0 sys=5.2
"cygman-2-6-7.dll" v0.0 ts=1970-01-01 00:00
30k 2014/05/26 C:\cygwin64\bin\cygmenuw-10.dll - os=4.0 img=0.0 sys=5.2
"cygmenuw-10.dll" v0.0 ts=1970-01-01 00:00
319k 2013/05/05 C:\cygwin64\bin\cygmpfr-4.dll - os=4.0 img=0.0 sys=5.2
"cygmpfr-4.dll" v0.0 ts=2013-05-05 13:40
53k 2014/05/26 C:\cygwin64\bin\cygncurses++w-10.dll - os=4.0 img=0.0 sys=5.2
"cygncurses++w-10.dll" v0.0 ts=1970-01-01 00:00
299k 2014/05/26 C:\cygwin64\bin\cygncursesw-10.dll - os=4.0 img=0.0 sys=5.2
"cygncursesw-10.dll" v0.0 ts=1970-01-01 00:00
208k 2014/08/19 C:\cygwin64\bin\cygp11-kit-0.dll - os=4.0 img=0.0 sys=5.2
"cygp11-kit-0.dll" v0.0 ts=2014-08-19 03:52
15k 2014/05/26 C:\cygwin64\bin\cygpanelw-10.dll - os=4.0 img=0.0 sys=5.2
"cygpanelw-10.dll" v0.0 ts=1970-01-01 00:00
273k 2014/08/27 C:\cygwin64\bin\cygpcre-1.dll - os=4.0 img=0.0 sys=5.2
"cygpcre-1.dll" v0.0 ts=2014-08-28 00:23
1580k 2013/03/11 C:\cygwin64\bin\cygperl5_14.dll - os=4.0 img=0.0 sys=5.2
"cygperl5_14.dll" v0.0 ts=2013-03-12 00:25
38k 2014/05/12 C:\cygwin64\bin\cygpipeline-1.dll - os=4.0 img=0.0 sys=5.2
"cygpipeline-1.dll" v0.0 ts=1970-01-01 00:00
41k 2013/10/21 C:\cygwin64\bin\cygpopt-0.dll - os=4.0 img=0.0 sys=5.2
"cygpopt-0.dll" v0.0 ts=2013-10-21 21:52
193k 2013/03/14 C:\cygwin64\bin\cygreadline7.dll - os=4.0 img=0.0 sys=5.2
"cygreadline7.dll" v0.0 ts=2013-03-14 11:14
96k 2014/09/04 C:\cygwin64\bin\cygsasl2-3.dll - os=4.0 img=0.0 sys=5.2
"cygsasl2-3.dll" v0.0 ts=2014-09-04 19:41
88k 2014/12/01 C:\cygwin64\bin\cygsmartcols-1.dll - os=4.0 img=0.0 sys=5.2
"cygsmartcols-1.dll" v0.0 ts=2014-12-01 23:56
744k 2014/08/19 C:\cygwin64\bin\cygsqlite3-0.dll - os=4.0 img=0.0 sys=5.2
"cygsqlite3-0.dll" v0.0 ts=2014-08-19 13:33
141k 2013/03/11 C:\cygwin64\bin\cygssh2-1.dll - os=4.0 img=0.0 sys=5.2
"cygssh2-1.dll" v0.0 ts=2013-03-11 11:42
379k 2014/08/07 C:\cygwin64\bin\cygssl-1.0.0.dll - os=4.0 img=0.0 sys=5.2
"cygssl-1.0.0.dll" v0.0 ts=1970-01-01 00:00
12k 2014/08/16 C:\cygwin64\bin\cygssp-0.dll - os=4.0 img=0.0 sys=5.2
"cygssp-0.dll" v0.0 ts=2014-08-15 21:10
892k 2014/08/16 C:\cygwin64\bin\cygstdc++-6.dll - os=4.0 img=0.0 sys=5.2
"cygstdc++-6.dll" v0.0 ts=2014-08-15 20:51
69k 2013/04/22 C:\cygwin64\bin\cygtasn1-6.dll - os=4.0 img=0.0 sys=5.2
"cygtasn1-6.dll" v0.0 ts=2013-04-22 01:25
53k 2014/05/26 C:\cygwin64\bin\cygticw-10.dll - os=4.0 img=0.0 sys=5.2
"cygticw-10.dll" v0.0 ts=1970-01-01 00:00
14k 2014/07/09 C:\cygwin64\bin\cyguuid-1.dll - os=4.0 img=0.0 sys=5.2
"cyguuid-1.dll" v0.0 ts=1970-01-01 00:00
30k 2013/11/15 C:\cygwin64\bin\cygwrap-0.dll - os=4.0 img=0.0 sys=5.2
"cygwrap-0.dll" v0.0 ts=2013-11-15 19:58
79k 2013/05/09 C:\cygwin64\bin\cygz.dll - os=4.0 img=0.0 sys=5.2
"cygz.dll" v0.0 ts=2013-05-09 22:20
3083k 2014/08/13 C:\cygwin64\bin\cygwin1.dll - os=4.0 img=0.0 sys=5.2
"cygwin1.dll" v0.0 ts=1970-01-01 00:00
Cygwin DLL version info:
DLL version: 1.7.32
DLL epoch: 19
DLL old termios: 5
DLL malloc env: 28
Cygwin conv: 181
API major: 0
API minor: 274
Shared data: 5
DLL identifier: cygwin1
Mount registry: 3
Cygwin registry name: Cygwin
Program options name: Program Options
Installations name: Installations
Cygdrive default prefix:
Build date:
Shared id: cygwin1S5
No Cygwin services found.
Cygwin Package Information
Last downloaded files to: C:\cygwin_data
Last downloaded files from: http://mirrors.xmission.com/cygwin/
Package Version Status
_autorebase 000243-1 OK
_update-info-dir 00328-1 OK
alternatives 1.3.30c-10 OK
autoconf 13-1 OK
autoconf2.1 2.13-12 OK
autoconf2.5 2.69-2 OK
automake 9-1 OK
automake1.10 1.10.3-2 OK
automake1.11 1.11.6-2 OK
automake1.12 1.12.6-2 OK
automake1.13 1.13.4-1 OK
automake1.14 1.14.1-1 OK
automake1.4 1.4p6-11 OK
automake1.5 1.5-11 OK
automake1.6 1.6.3-12 OK
automake1.7 1.7.9-11 OK
automake1.8 1.8.5-11 OK
automake1.9 1.9.6-11 OK
base-cygwin 3.3-1 OK
base-files 4.2-3 OK
bash 4.1.17-9 OK
binutils 2.24.51-5 OK
bzip2 1.0.6-2 OK
ca-certificates 1.97-2 OK
coreutils 8.23-2 OK
csih 0.9.7-1 OK
cygrunsrv 1.61-1 OK
cygutils 1.4.14-1 OK
cygwin 1.7.32-1 OK
dash 0.5.8-2 OK
diffutils 3.3-2 OK
editrights 1.02-1 OK
file 5.19-1 OK
findutils 4.5.12-1 OK
gawk 4.1.1-1 OK
getent 2.18.90-2 OK
gnupg 1.4.18-1 OK
grep 2.16-1 OK
groff 1.22.2-2 OK
gzip 1.4-1 OK
hostname 3.13-1 OK
info 5.2-3 OK
ipc-utils 1.0-2 OK
less 458-1 OK
libargp 20110921-2 OK
libattr1 2.4.46-1 OK
libblkid1 2.24.2-1 OK
libbz2_1 1.0.6-2 OK
libcom_err2 1.42.10-1 OK
libcrypt0 1.1-1 OK
libcurl4 7.38.0-1 OK
libdb5.3 5.3.21-1 OK
libedit0 20130712-1 OK
libexpat1 2.1.0-3 OK
libffi6 3.0.13-1 OK
libgcc1 4.8.3-3 OK
libgdbm4 1.11-1 OK
libgmp10 6.0.0a-1 OK
libgssapi_krb5_2 1.12.2-1 OK
libiconv 1.14-1 OK
libiconv2 1.14-1 OK
libidn11 1.26-1 OK
libintl-devel 0.18.3.2-2 OK
libintl8 0.18.3.2-2 OK
libk5crypto3 1.12.2-1 OK
libkrb5_3 1.12.2-1 OK
libkrb5support0 1.12.2-1 OK
liblzma5 5.0.5-1 OK
libmpfr4 3.1.2-1 OK
libncursesw10 5.9-20140524-1 OK
libopenldap2_4_2 2.4.35-1 OK
libopenssl100 1.0.1i-1 OK
libp11-kit0 0.20.4-1 OK
libpcre1 8.35-1 OK
libpipeline1 1.3.0-3 OK
Empty package libpopt0
libpopt0 1.16-1 OK
libreadline7 6.2-1 OK
libsasl2_3 2.1.26-8 OK
libsmartcols1 2.25.2-1 OK
libsqlite3_0 3.8.6-1 OK
libssh2_1 1.4.2-1 OK
libssp0 4.8.3-3 OK
libstdc++6 4.8.3-3 OK
libtasn1_6 3.3-1 OK
libuuid-devel 2.24.2-1 OK
libuuid1 2.24.2-1 OK
libwrap0 7.6-22 OK
login 1.10-10 OK
lynx 2.8.7-2 OK
m4 1.4.17-1 OK
make 4.0-2 OK
man-db 2.6.7-2 OK
mintty 1.2-beta1-1 OK
nano 2.2.6-1 OK
openssh 6.7p1-1 OK
openssl 1.0.1j-2 OK
p11-kit 0.20.4-1 OK
p11-kit-trust 0.20.4-1 OK
perl 5.14.4-1 OK
ping 1.0.2-1 OK
popt 1.16-1 OK
procps 3.2.8-3 OK
python 2.7.8-1 OK
python3 3.2.5-4 OK
rebase 4.4.1-1 OK
run 1.3.3-1 OK
sed 4.2.2-3 OK
tar 1.27.1-1 OK
terminfo 5.9-20140524-1 OK
texinfo 5.2-2 OK
tzcode 2013c-1 OK
util-linux 2.24.2-1 OK
vim 7.4.417-1 OK
vim-common 7.4.417-1 OK
vim-minimal 7.4.417-1 OK
which 2.20-2 OK
windows-default-manifest 6.3-1 OK
xxd 7.4.417-1 OK
xz 5.0.5-1 OK
zlib0 1.2.8-1 OK
Use -h to see help about each section
[-- Attachment #3: Type: text/plain, Size: 218 bytes --]
--
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
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Mintty Crash on Exit after SSH on Windows 10
2015-09-17 8:10 Mintty Crash on Exit after SSH on Windows 10 Bryan Tong
@ 2015-09-17 10:14 ` Marco Atzeri
2015-09-17 21:05 ` Mintty Hang " Thomas Wolff
2015-09-30 5:10 ` Mintty Crash " Bryan Tong
1 sibling, 1 reply; 12+ messages in thread
From: Marco Atzeri @ 2015-09-17 10:14 UTC (permalink / raw)
To: cygwin
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.
>
> 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" ?
> I can almost always reproduce this after working on remote servers.
> However when I try to do it on command it happen every time.
--
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
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Mintty Hang on Exit after SSH on Windows 10
2015-09-17 10:14 ` Marco Atzeri
@ 2015-09-17 21:05 ` Thomas Wolff
2015-09-17 21:36 ` Warren Young
0 siblings, 1 reply; 12+ messages in thread
From: Thomas Wolff @ 2015-09-17 21:05 UTC (permalink / raw)
To: cygwin
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
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Mintty Hang on Exit after SSH on Windows 10
2015-09-17 21:05 ` Mintty Hang " Thomas Wolff
@ 2015-09-17 21:36 ` Warren Young
0 siblings, 0 replies; 12+ messages in thread
From: Warren Young @ 2015-09-17 21:36 UTC (permalink / raw)
To: The Cygwin Mailing List
On Sep 17, 2015, at 3:05 PM, Thomas Wolff wrote:
>
>> 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?
It’s probably some bit of voodoo learned in a situation where Ctrl-D alone didn’t do what the OP wanted. Ctrl-A goes to the beginning of the line in Bash’s default input mode, so it’s a no-op any time a subsequent Ctrl-D would exit the shell.
If there is input text at the shell prompt, Ctrl-A will go to the beginning of it, but Ctrl-D in that case does a backwards delete, like DEL on an IBM PC keyboard. So again, there is no case I can think of where Ctrl-A + Ctrl-D is a better way to exit the shell than just Ctrl-D.
--
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
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Mintty Crash on Exit after SSH on Windows 10
2015-09-17 8:10 Mintty Crash on Exit after SSH on Windows 10 Bryan Tong
2015-09-17 10:14 ` Marco Atzeri
@ 2015-09-30 5:10 ` Bryan Tong
2015-09-30 5:15 ` Bryan Tong
1 sibling, 1 reply; 12+ messages in thread
From: Bryan Tong @ 2015-09-30 5:10 UTC (permalink / raw)
To: cygwin
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 <contact@nullivex.com> 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
--
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
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Mintty Crash on Exit after SSH on Windows 10
2015-09-30 5:10 ` Mintty Crash " Bryan Tong
@ 2015-09-30 5:15 ` Bryan Tong
2015-09-30 5:21 ` Bryan Tong
2015-09-30 8:54 ` Thomas Wolff
0 siblings, 2 replies; 12+ messages in thread
From: Bryan Tong @ 2015-09-30 5:15 UTC (permalink / raw)
To: cygwin
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 <contact@nullivex.com> 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 <contact@nullivex.com> 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
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Mintty Crash on Exit after SSH on Windows 10
2015-09-30 5:15 ` Bryan Tong
@ 2015-09-30 5:21 ` Bryan Tong
2015-11-21 1:19 ` Bryan Tong
2015-09-30 8:54 ` Thomas Wolff
1 sibling, 1 reply; 12+ messages in thread
From: Bryan Tong @ 2015-09-30 5:21 UTC (permalink / raw)
To: cygwin
Sorry for the extra replies.
I am going to try to do some more research on the issue. After letting
a mintty window sit open and typing absolutely nothing inside it and
then closing it about 5 minutes later it hangs on exit.
Very strange behavior. Im not seeing it so bad on my other computers
but still intermittent on them.
On Tue, Sep 29, 2015 at 11:15 PM, Bryan Tong <contact@nullivex.com> wrote:
> 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 <contact@nullivex.com> 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 <contact@nullivex.com> 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
--
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
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Mintty Crash on Exit after SSH on Windows 10
2015-09-30 5:15 ` Bryan Tong
2015-09-30 5:21 ` Bryan Tong
@ 2015-09-30 8:54 ` Thomas Wolff
1 sibling, 0 replies; 12+ messages in thread
From: Thomas Wolff @ 2015-09-30 8:54 UTC (permalink / raw)
To: cygwin
Am 30.09.2015 um 07:15 schrieb Bryan Tong:
> 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.
That sounds like it. Maybe some "exit trap" or other magic that you set
up in your shell profile? If you don't mind, you could send it to me so
I can check (for bash, that would be .profile or .bash_profile or
.bash_login and .bashrc in your $HOME, and possibly something from /etc
in case you changed that).
------
Thomas
> On Tue, Sep 29, 2015 at 11:10 PM, Bryan Tong <contact@nullivex.com> 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 <contact@nullivex.com> 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
--
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
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Mintty Crash on Exit after SSH on Windows 10
2015-09-30 5:21 ` Bryan Tong
@ 2015-11-21 1:19 ` Bryan Tong
2017-11-03 20:02 ` Rick Maus
0 siblings, 1 reply; 12+ messages in thread
From: Bryan Tong @ 2015-11-21 1:19 UTC (permalink / raw)
To: cygwin
Hello,
I wanted to do one last follow up here. This issue has cleared up on
all of my computers. The only environmental change was Windows update.
Thus, my conclusion is that this was a Microsoft bug rather than a
Mintty / Cygwin one and it has been cleared up with the latest
updates.
Thanks for the help guys!
On Tue, Sep 29, 2015 at 11:21 PM, Bryan Tong <contact@nullivex.com> wrote:
> Sorry for the extra replies.
>
> I am going to try to do some more research on the issue. After letting
> a mintty window sit open and typing absolutely nothing inside it and
> then closing it about 5 minutes later it hangs on exit.
>
> Very strange behavior. Im not seeing it so bad on my other computers
> but still intermittent on them.
>
> On Tue, Sep 29, 2015 at 11:15 PM, Bryan Tong <contact@nullivex.com> wrote:
>> 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 <contact@nullivex.com> 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 <contact@nullivex.com> 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
>
>
>
> --
> 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
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Mintty Crash on Exit after SSH on Windows 10
2015-11-21 1:19 ` Bryan Tong
@ 2017-11-03 20:02 ` Rick Maus
2018-04-23 15:48 ` cyg
0 siblings, 1 reply; 12+ messages in thread
From: Rick Maus @ 2017-11-03 20:02 UTC (permalink / raw)
To: cygwin
I am experiencing a similar situation on a recently reimaged Windows 10
computer in a large corporate environment, namely:
* Either typing "exit" or clicking the Windows close [X] button from a
Cygwin bash terminal (mintty under the hood) results in the process hanging
with it either eventually closing after a few minutes (or) Windows
indicating the process is not responding and offering to terminate it.
* Moving my home directory out of the way and recreating a basic home
directory did NOT work around the situation for me which is different than
the experience Bryan Tong described.
I have noticed that our organization is intentionally slower to roll out
Windows updates to our environment, so I am keeping my fingers crossed for
that situation. If anyone wants a thread dump to investigate, please feel
free to reach out.
--
Sent from: http://cygwin.1069669.n5.nabble.com/Cygwin-list-f3.html
--
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
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Mintty Crash on Exit after SSH on Windows 10
2017-11-03 20:02 ` Rick Maus
@ 2018-04-23 15:48 ` cyg
2018-04-23 17:38 ` Thomas Wolff
0 siblings, 1 reply; 12+ messages in thread
From: cyg @ 2018-04-23 15:48 UTC (permalink / raw)
To: cygwin
I've been experiencing this same issue. Did anyone ever come up with a
solution?
--
Sent from: http://cygwin.1069669.n5.nabble.com/Cygwin-list-f3.html
--
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
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Mintty Crash on Exit after SSH on Windows 10
2018-04-23 15:48 ` cyg
@ 2018-04-23 17:38 ` Thomas Wolff
0 siblings, 0 replies; 12+ messages in thread
From: Thomas Wolff @ 2018-04-23 17:38 UTC (permalink / raw)
To: cygwin
Am 23.04.2018 um 17:48 schrieb cyg@david.perd.org:
> I've been experiencing this same issue. Did anyone ever come up with a solution?
"this same issue" is a bit fuzzy after more than two years. Please
describe your symptoms, mention the mintty version, the output of `type
ssh`, and please check with https://github.com/mintty/mintty/issues/745
Thomas
---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus
--
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
^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2018-04-23 17:38 UTC | newest]
Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-09-17 8:10 Mintty Crash on Exit after SSH on Windows 10 Bryan Tong
2015-09-17 10:14 ` Marco Atzeri
2015-09-17 21:05 ` Mintty Hang " Thomas Wolff
2015-09-17 21:36 ` 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
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).