starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-24 16:05:21 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

ssh session becomes unresponsive when changing VPN #10130

New Issue
Closed
opened 2026-01-31 02:13:19 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 02:13:19 +00:00
Owner
Copy Link

Originally created by @suBOTai3 on GitHub (Aug 13, 2020).

Environment

Windows 10 x64 build number: 20161.1000
Windows Terminal version (if applicable):

Any other software?
WSL2 Ubuntu 20.04

Steps to reproduce

  • connect to VPN
  • open terminal in Ubuntu / WSL2
  • ssh to another machine
  • while the ssh session is open, change vpn to another vpn

Expected behavior

ssh session should exit

Actual behavior

ssh terminal becomes unresponsive. Cursor still flickers, so its not frozen, just not responding to keyboard input

terminal

Originally created by @suBOTai3 on GitHub (Aug 13, 2020). # Environment ```Windows Windows 10 x64 build number: 20161.1000 Windows Terminal version (if applicable): Any other software? WSL2 Ubuntu 20.04 ``` # Steps to reproduce * connect to VPN * open terminal in Ubuntu / WSL2 * ssh to another machine * while the ssh session is open, change vpn to another vpn # Expected behavior ssh session should exit # Actual behavior ssh terminal becomes unresponsive. Cursor still flickers, so its not frozen, just not responding to keyboard input ![terminal](https://user-images.githubusercontent.com/5020751/90119676-25d91400-dd5a-11ea-8841-a3c48c7520fd.png)
claunia added the Issue-QuestionNeeds-TriageResolution-ExternalNeeds-Tag-Fix labels 2026-01-31 02:13:19 +00:00
claunia commented 2026-01-31 02:13:21 +00:00
Author
Owner
Copy Link

@fran-f commented on GitHub (Aug 13, 2020):

Does this happen only in Terminal? Does it work fine in the basic WSL console?

@fran-f commented on GitHub (Aug 13, 2020): Does this happen only in Terminal? Does it work fine in the basic WSL console?
claunia commented 2026-01-31 02:13:21 +00:00
Author
Owner
Copy Link

@suBOTai3 commented on GitHub (Aug 13, 2020):

Hi @fran-f

I've just been able to replicate in basic wsl console, so I suppose that would have to be logged under a different issue then as it's not strictly related to the terminal project

Thanks for your support

@suBOTai3 commented on GitHub (Aug 13, 2020): Hi @fran-f I've just been able to replicate in basic wsl console, so I suppose that would have to be logged under a different issue then as it's not strictly related to the terminal project Thanks for your support
claunia commented 2026-01-31 02:13:21 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 13, 2020):

Yea, this sounds like something that should be filed against ssh itself, though I don't know where their issue tracker is. Thanks for following up!

@zadjii-msft commented on GitHub (Aug 13, 2020): Yea, this sounds like something that should be filed against `ssh` itself, though I don't know where their issue tracker is. Thanks for following up!
claunia commented 2026-01-31 02:13:21 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Aug 13, 2020):

Isn’t changing the VPN like disconnecting the network? Unless you’re using software that has automatic network failover support, it’s going to fail any active network connections when you do that. That’s like pulling the network cable out and wondering why your file download stopped working 🤨

@DHowett commented on GitHub (Aug 13, 2020): Isn’t changing the VPN like _disconnecting the network_? Unless you’re using software that has automatic network failover support, it’s going to fail _any active network connections_ when you do that. That’s like pulling the network cable out and wondering why your file download stopped working 🤨
claunia commented 2026-01-31 02:13:21 +00:00
Author
Owner
Copy Link

@suBOTai3 commented on GitHub (Aug 14, 2020):

Hi @DHowett

Yes you're right that is an accurate analogue. But at the same time, good software should indicate that there is no longer a connection when attempting to continue inputting characters.

But remember, as @fran-f and I concluded in our previous messages - this should rather be logged on the WSL2 github page because WSL2 is failing to notify the end user that you cannot continue input.

Think of it like a browser. If for some reason your internet connection drops / the network is disconnected, the browser doesn't stop being responsive. It still accepts input. It's only when you attempt to launch an action that requires a server connection / an update that the UI responds, and then it responds with the appropriate error message.

What I was expecting, as an end user, is to type and then be informed that the input cannot be processed....or something similar. I'm not sure how that can be achieved, but the current solution of a 'blank screen' with a blinking cursor made be do a double take the first couple of times.

@suBOTai3 commented on GitHub (Aug 14, 2020): Hi @DHowett Yes you're right that is an accurate analogue. But at the same time, good software should indicate that there is no longer a connection when attempting to continue inputting characters. But remember, as @fran-f and I concluded in our previous messages - this should rather be logged on the WSL2 github page because WSL2 is failing to notify the end user that you cannot continue input. Think of it like a browser. If for some reason your internet connection drops / the network is disconnected, the browser doesn't stop being responsive. It still accepts input. It's only when you attempt to launch an action that requires a server connection / an update that the UI responds, and then it responds with the appropriate error message. What I was expecting, as an end user, is to type and then be informed that the input cannot be processed....or something similar. I'm not sure how that can be achieved, but the current solution of a 'blank screen' with a blinking cursor made be do a double take the first couple of times.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Question Needs-Tag-Fix Needs-Triage Resolution-External
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#10130
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?