-
-
Notifications
You must be signed in to change notification settings - Fork 136
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hangs on connection open/close #22
Comments
Hi @bobvandevijver ,
This is the same bug commented in #23 , futhermore the same described in #15 . If we can provide more feedback then @cyd01 perhaps can fix it. Regards. |
While the second part is indeed now solved with #23, the first part (hanging on opening) still holds. Might have something to do with port forwarding? |
Hi, As I described in #23 (comment) when using TCP tunnels (or Proxies) for the connections, the session enters in a stalled state. I recommend to add some "close&reconnect" as this will simplifies a lot this type of problems. |
This issue also happens with connection that do not use any tunnels or proxies. |
In this case I recommend the simple "close&reconnect" command as the most simple workaround. |
That won't work, as it completely hangs ("this application is not responding"). At the moment it does respond, the connection is opened correctly. |
Hi @bobvandevijver , I recommend to implement a new "close&reconnect" command. It doesn't exist at time! |
Again, that will never work for this scenario. The application is completely unresponsive, Windows nags about it when clicking the window. It will never show any dialog on whatever input you provide to the window (not the ssh session)! |
Ok, now I understand you. In my day work when the error appears the Menu of the KiTTY continues working. Only after using "Repeat key exchange" (when the connection is lost, but the session is not detected as closed) the KiTTY goes unresponsive. I'm sure a bug exists in the handle of the session when a network error appears. Regards. |
Hi @bobvandevijver , Please, try with the new version 0.71.0.5. And then if your problem is gone, then close this issue please. Regards. |
No, it is not fixed. |
Can confirm that it's not fixed in 0.71.0.5. Also the problem is the same with the latest putty client and Windows 10 1903. |
I think this one is a windows related problem. |
and even the build in client you can open with a cmd line hung up. perhaps @bobvandevijver you can verify that with the build in client on the windows command line |
@thomasgg23 Might well be the case. I also see other network glitches.. |
Hi @thomasgg23 , Please, check if the problem continues in the new 0.71.0.6p release. |
Nope, 0.71.0.6 still has the same problem |
Still same behavior with 0.71.0.6p. Will continue to watch on the weekend. |
I seem to have no issues after a fresh restart of the laptop, but after it has been in modern standby, the connection hangs on start. |
Hi @bobvandevijver , Last version resolves your problem? |
For me it seems to be resolved |
Then I suggest to the original author and to @cyd01 to close this issue. |
I want to test it first, which I can probably do tomorrow. If satisfied, I will close it :) |
Issue still seems to be there, but a lot less frequent. I will try to figure out whether we can blame Windows and the networking stack for this, as it mostly seems to happen after modern standby. |
Hi @bobvandevijver , Please, try version 0.73.2.3. I feel the issue is fully resolved. Regards. |
I cannot try it due to #105, that needs to be resolved first. |
Hi @bobvandevijver , The issue #105 will never be solved. The main developer can't do anything to resolve this problem. The true is that the McAfee software is doing wrong. As it detects an unsigned binary and this binary is a fork of a PuTTY, then it marks it as a malware. But it isn't. If you want to solve it, then write to McAfee. My recomendation is to disable it. Please, someone other can check the last version? We need to know if the problem is fixed. Regards. |
First off all, that's not how antivirus works, and yes, the developer can do something about it. Secondly, I'm not using McAfee. Thirdly, the uncompressed version has no issues, so I tested now with that one. The issue still persist. |
OK @bobvandevijver , then please explain what the developer can do to overcome the issue. Personally I don't have any idea about how to resolve the problem. And I feel that @cyd01 doesn't know it either! Regards. |
Hi @bobvandevijver , The issue of the false-positive malware detection is commented in #115 . I suggest to post in this thread any comments than can help to solve this problem. Regarding the hangs on reconnection @thomasgg23 has commented that from him the problem has gone in the last versions. Futhermore, some recent enhancements are incorporated in the last version regarding the reconnection part. The only missing funciton at time is the forwarding restart. So, I suggest to @bobvandevijver or @cyd01 to close this issue... if you think that this problem is solved (almost partially and no referenced in other issues). You agree? 😉 |
I wont close this, as it is not resolved. |
Please, can you explain what is not resolved? |
I'm sorry @lars18th, I was under the assumption that your knew what this ticket is about. Maybe you should stop commenting if you do not have anything useful to add. Repeating the same question is not going to solve this problem by some sort of magic. KiTTY still hangs when opening a connection, which is most reproducible after a longer modern standby session. Other SSH clients (such as in WSL Debian) do not have this problem. |
Not reproduced for a while. |
I'm using kitten ssh, but seems the ssh master process continue running and don't allow that close the terminal. |
It seems that with the release of Windows 10 1903 kitty sometimes hangs when opening a session: the terminal window opens unresponsive (and is empty), and after a few seconds it proceeds as you would normally expect.
Secondly, when losing a session, it previously was possible to use any key to reconnect, but it does not seem to respond to that anymore (it actually warns when closing that the connection would still be activity, while the taskbar icon clearly indicates the connection is no longer there).
The text was updated successfully, but these errors were encountered: