starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

[WSL on Terminal] Forced disconnections from tmux over SSH sessions leaves input handling in a broken state. #9610

New Issue
Closed
opened 2026-01-31 01:59:11 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 01:59:11 +00:00
Owner
Copy Link

Originally created by @munael on GitHub (Jul 14, 2020).

Environment

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

Any other software?
Remote host: Ubuntu 16.04 LTS
Tmux, ssh

Steps to reproduce

  1. Open a WSL session in .
  2. Connect to some remote linux machine.
  3. Configure SSH to use mouse events:
set -g mouse on
  1. Start a new tmux session and add some panes, move around them using the mouse.
  2. Disconnect computer from the Internet.
  3. A few seconds later the SSH client boots you back up to WSL.
  4. Click anywhere in the window. You should see characters like:
0;63;12M0;63;12m

If is Windows Terminal, you should see the bug. If is the bare WSL executable, you shouldn't see the bug.

Expected behavior

Some configuration is being passed to the terminal to enable mouse handling and Windows Terminal honors it for longer than the lifetime of the program that requested it.

It might be the more logical design, but it's a very irritating UX issue that doesn't manifest in older terminals. Also, if it were about cleanup, I would expect that starting the same program again and exiting it normally would fix the issue, but it doesn't.

Actual behavior

  1. Click anywhere in the window. You should see characters like:
0;63;12M0;63;12m

If is Windows Terminal, you should see the bug. If is the bare WSL executable, you shouldn't see the bug.

Originally created by @munael on GitHub (Jul 14, 2020). # Environment ```none Windows build number: 10.0.18363.0 Windows Terminal version (if applicable): 1.0.1401.0 Any other software? Remote host: Ubuntu 16.04 LTS Tmux, ssh ``` # Steps to reproduce 1. Open a WSL session in <X>. 2. Connect to some remote linux machine. 3. Configure SSH to use mouse events: ``` set -g mouse on ``` 4. Start a new tmux session and add some panes, move around them using the mouse. 5. Disconnect computer from the Internet. 6. A few seconds later the SSH client boots you back up to WSL. 7. Click anywhere in the window. You should see characters like: ``` 0;63;12M0;63;12m ``` If <X> is Windows Terminal, you should see the bug. If <X> is the bare WSL executable, you **shouldn't** see the bug. # Expected behavior Some configuration is being passed to the terminal to enable mouse handling and Windows Terminal honors it for longer than the lifetime of the program that requested it. It might be the more logical design, but it's a very irritating UX issue that doesn't manifest in older terminals. Also, if it were about cleanup, I would expect that starting the same program again and exiting it normally would fix the issue, but it doesn't. # Actual behavior <!-- What's actually happening? --> 7. Click anywhere in the window. You should see characters like: ``` 0;63;12M0;63;12m ``` If <X> is Windows Terminal, you should see the bug. If <X> is the bare WSL executable, you **shouldn't** see the bug.
claunia added the Resolution-By-DesignNeeds-Tag-Fix labels 2026-01-31 01:59:12 +00:00
claunia commented 2026-01-31 01:59:13 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 14, 2020):

Any application that changes the global terminal state is expected to restore it when it exits. This is common across every terminal emulator in existence. Unfortunately, there is no way for WT to know that the remote application (ESPECIALLY over ssh) has been terminated and clean up after it.

This will happen even in the "normal" WSL instance outside of terminal.

@DHowett commented on GitHub (Jul 14, 2020): Any application that changes the global terminal state is expected to restore it when it exits. This is common across every terminal emulator in existence. Unfortunately, there is no way for WT to know that the remote application (ESPECIALLY over ssh) has been terminated and clean up after it. This will happen even in the "normal" WSL instance outside of terminal.
claunia commented 2026-01-31 01:59:13 +00:00
Author
Owner
Copy Link

@munael commented on GitHub (Jul 14, 2020):

Couldn't get it to trigger with the basic shell used by WSL :/

@munael commented on GitHub (Jul 14, 2020): Couldn't get it to trigger with the basic shell used by WSL :/
claunia commented 2026-01-31 01:59:13 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 14, 2020):

Here's an example of it happening with PuTTY:

terminal_weird_state

@DHowett commented on GitHub (Jul 14, 2020): Here's an example of it happening with PuTTY: ![terminal_weird_state](https://user-images.githubusercontent.com/189190/87392977-531b8200-c562-11ea-8906-8efa53719909.gif)
claunia commented 2026-01-31 01:59:13 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 14, 2020):

And just to close the loop -- I tested this in the standard console host (which WSL uses) as well:

terminal_mouse_mode_conserved

@DHowett commented on GitHub (Jul 14, 2020): And just to close the loop -- I tested this in the standard console host (which WSL uses) as well: ![terminal_mouse_mode_conserved](https://user-images.githubusercontent.com/189190/87466365-f99b6d80-c5ca-11ea-924a-56c7906c46eb.gif)
claunia commented 2026-01-31 01:59:14 +00:00
Author
Owner
Copy Link

@munael commented on GitHub (Jul 15, 2020):

That's unfortunate :/ Need to make it so SSH clears such vestigial config after unexpectedly disconnecting. Needs a script. There doesn't seem to be a clean "return terminal to original state" flag in SSH. Or I don't know the terms to look for.

@munael commented on GitHub (Jul 15, 2020): That's unfortunate :/ Need to make it so SSH clears such vestigial config after unexpectedly disconnecting. Needs a script. There doesn't seem to be a clean "return terminal to original state" flag in SSH. Or I don't know the terms to look for.
claunia commented 2026-01-31 01:59:14 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 15, 2020):

SSH can’t do this because there’s no way for it to know what state the terminal was in. Your best bet is to use the reset command in WSL, which emits a “hard reset” (restore terminal to default configuration) escape sequence.

@DHowett commented on GitHub (Jul 15, 2020): SSH can’t do this because there’s no way for it to know what state the terminal was in. Your best bet is to use the `reset` command in WSL, which emits a “hard reset” (restore terminal to default configuration) escape sequence.
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 Needs-Tag-Fix Resolution-By-Design
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#9610
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?