SSH disconnected session is hardly recovered #8770

Closed
opened 2026-01-31 01:37:32 +00:00 by claunia · 2 comments
Owner

Originally created by @gcoppola8 on GitHub (Jun 3, 2020).

Environment

Windows build number: Microsoft Windows NT 10.0.18363.0
Windows Terminal version (if applicable): 1.0.1401.0

Any other software?

WSL with debian

Steps to reproduce

  • Open tab with debian console (WSL)
  • Connect ssh to a remote machine
  • Provoke reset connection due inactivity ( I say provoke because it is unproductive to stay there waiting the connection to reset by time).

Expected behavior

I expect to see a disconnected message, or to return to debian local console.

Actual behavior

What happens is that I continue to see the last message from the ssh connection, and clicking "Enter" or sending "CTRL+C" I am not able to go back to my debian environment. If not closing the tab and opening another one.

Originally created by @gcoppola8 on GitHub (Jun 3, 2020). # Environment ``` Windows build number: Microsoft Windows NT 10.0.18363.0 Windows Terminal version (if applicable): 1.0.1401.0 ``` Any other software? ``` WSL with debian ``` # Steps to reproduce - Open tab with debian console (WSL) - Connect ssh to a remote machine - Provoke reset connection due inactivity ( I say provoke because it is unproductive to stay there waiting the connection to reset by time). # Expected behavior I expect to see a disconnected message, or to return to debian local console. # Actual behavior What happens is that I continue to see the last message from the ssh connection, and clicking "Enter" or sending "CTRL+C" I am not able to go back to my debian environment. If not closing the tab and opening another one.
claunia added the Issue-QuestionNeeds-Tag-FixResolution-Answered labels 2026-01-31 01:37:33 +00:00
Author
Owner

@DHowett commented on GitHub (Jun 3, 2020):

If you're not getting returned to your Debian session, and you ran ssh from inside Debian, there is nothing terminal can do for you. If SSH hangs, that's SSH's fault.

@DHowett commented on GitHub (Jun 3, 2020): If you're not getting returned to your Debian session, and you ran ssh from _inside Debian_, there is **nothing** terminal can do for you. If SSH hangs, that's SSH's fault.
Author
Owner

@gcoppola8 commented on GitHub (Jun 5, 2020):

Hello,
but if I use "Debian" application from the start menu, it doesn't have the same behavior, and in alternative product like bitvise ssh client I get a "disconnected" message at the center of the terminal.
And in ssh under native debian again I immediately get the control of the session.
Because this behavior I found it only using Windows Terminal, I thought to report here.

@gcoppola8 commented on GitHub (Jun 5, 2020): Hello, but if I use "Debian" application from the start menu, it doesn't have the same behavior, and in alternative product like bitvise ssh client I get a "disconnected" message at the center of the terminal. And in ssh under native debian again I immediately get the control of the session. Because this behavior I found it only using Windows Terminal, I thought to report here.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#8770