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

terminal lost scrollbar after an unexcepted close of ssh/tmux #19760

New Issue
Closed
opened 2026-01-31 06:52:49 +00:00 by claunia · 1 comment
claunia commented 2026-01-31 06:52:49 +00:00
Owner
Copy Link

Originally created by @clor09 on GitHub (Apr 24, 2023).

Windows Terminal version

1.16.10262.0

Windows build number

10.0.22621.0

Other Software

OpenSSH_for_Windows_8.6p1, LibreSSL 3.4.3
tmux 3.1c

Steps to reproduce

  1. open a new terminal tab
  2. run some commands(eg. ps) to get long output. the scrollbar appears, and you can see history output just by scroll up
  3. ssh to a remote machine(linux better~)
  4. start tmux on remote machine. do something, like split a pane, run some commands but keep the tmux session open
  5. switch to another tab, in pwsh do kill -name ssh , (make sure this is the ssh process you have made above)
  6. switch back to the previous tab, the ssh process get killed, but the scroll bar does not come back, you can no longer scroll up to see the history. run ps to make a long output, and still, you cant see the full output by scroll up any more

Expected Behavior

if the remote session lost by any means, terminal should recover to a normal status, and the history need to be seen (both before and after the ssh/tmux(crashed or normal quit))

Actual Behavior

output before the ssh/tmux session "lost", after the ssh/tmux session crashed terminal was left in a bad status. long output can no longer be seen by scroll up

Originally created by @clor09 on GitHub (Apr 24, 2023). ### Windows Terminal version 1.16.10262.0 ### Windows build number 10.0.22621.0 ### Other Software OpenSSH_for_Windows_8.6p1, LibreSSL 3.4.3 tmux 3.1c ### Steps to reproduce 1. open a new terminal tab 2. run some commands(eg. ps) to get long output. the scrollbar appears, and you can see history output just by scroll up 3. ssh to a remote machine(linux better~) 4. start tmux on remote machine. do something, like split a pane, run some commands but keep the tmux session open 5. switch to another tab, in pwsh do `kill -name ssh` , (make sure this is the ssh process you have made above) 6. switch back to the previous tab, the ssh process get killed, but the scroll bar does not come back, you can no longer scroll up to see the history. run `ps` to make a long output, and still, you cant see the full output by scroll up any more ### Expected Behavior if the remote session lost by any means, terminal should recover to a normal status, and the history need to be seen (both before and after the ssh/tmux(crashed or normal quit)) ### Actual Behavior output before the ssh/tmux session "lost", after the ssh/tmux session crashed terminal was left in a bad status. long output can no longer be seen by scroll up
claunia added the Issue-QuestionNeeds-TriageResolution-Answered labels 2026-01-31 06:52:49 +00:00
claunia commented 2026-01-31 06:52:50 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 24, 2023):

Unfortunately, this is something that the Terminal can't fix. This is behavior that's pretty well-conserved across different terminal emulators out there. If one application changes the modes of the terminal, and doesn't shut down cleanly (to reset those modes), the terminal has no way of knowing how to reset those modes automatically. In this specific case, tmux entered the "alternate screen buffer", and didn't have the opportunity to switch back out.

Usually, in this state, a reset should bring the terminal back to a working state. I dunno if there's an easy way to do that from CMD or powershell though - that might be a WSL thing.






<idle thought> Maybe we could add an action for manually toggling which buffer is active? Obviously, this would break apps that think they're in the other one, but maybe? Uhg that would require plumbing through to conpty though, that might be impossible.

@zadjii-msft commented on GitHub (Apr 24, 2023): Unfortunately, this is something that the Terminal can't fix. This is behavior that's pretty well-conserved across different terminal emulators out there. If one application changes the modes of the terminal, and doesn't shut down cleanly (to reset those modes), the terminal has no way of knowing how to reset those modes automatically. In this specific case, `tmux` entered the "alternate screen buffer", and didn't have the opportunity to switch back out. Usually, in this state, a `reset` _should_ bring the terminal back to a working state. I dunno if there's an easy way to do that from CMD or powershell though - that might be a WSL thing. <br><br><br><br> \<idle thought> Maybe we could add an action for manually toggling which buffer is active? Obviously, this would break apps that think they're in the other one, but _maybe_? Uhg that would require plumbing through to conpty though, that might be impossible.
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-Triage Resolution-Answered
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#19760
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?