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

Bug Report: Reaction to Keyboard input is anomalous #1371

New Issue
Closed
opened 2026-01-30 22:23:54 +00:00 by claunia · 7 comments
claunia commented 2026-01-30 22:23:54 +00:00
Owner
Copy Link

Originally created by @MelulekiDube on GitHub (May 26, 2019).

Environment

Windows build number: [Version 10.0.18898.1000]
Windows Terminal version (if applicable): 0.0.1.0

Steps to reproduce

  1. Start terminal
  2. ssh to a remote host
  3. disconnect from the internet while connected to the network
  4. Try to type something on the terminal and observe

Expected behavior

The keyboard input should be working properly

Actual behavior

Weird reaction to input. Although on enter the write input is processed.

issue
Also if an editor like vim was open as can be seen the screen is not cleared on loss of connection.
It will be nice to have the normal error telling you of a timeout error and the terminal goes back to working as it was working before.

Originally created by @MelulekiDube on GitHub (May 26, 2019). <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: [Version 10.0.18898.1000] Windows Terminal version (if applicable): 0.0.1.0 ``` # Steps to reproduce 1. Start terminal 1. ssh to a remote host 1. disconnect from the internet while connected to the network 1. Try to type something on the terminal and observe <!-- A description of how to trigger this bug. --> # Expected behavior The keyboard input should be working properly <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> # Actual behavior Weird reaction to input. Although on enter the write input is processed. <!-- What's actually happening? --> ![issue](https://user-images.githubusercontent.com/24409733/58383529-5bb89e00-7fd8-11e9-9151-7fb4ccb1a3e1.gif) Also if an editor like vim was open as can be seen the screen is not cleared on loss of connection. It will be nice to have the normal error telling you of a timeout error and the terminal goes back to working as it was working before.
claunia added the Issue-QuestionArea-InputResolution-ExternalProduct-Terminal labels 2026-01-30 22:23:54 +00:00
claunia commented 2026-01-30 22:23:55 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 28, 2019):

Is this wsl ssh or the built-in ssh.exe?

@zadjii-msft commented on GitHub (May 28, 2019): Is this wsl `ssh` or the built-in `ssh.exe`?
claunia commented 2026-01-30 22:23:55 +00:00
Author
Owner
Copy Link

@MelulekiDube commented on GitHub (May 28, 2019):

@zadjii-msft This is with ssh.exe. With wsl the issue is the screen is not cleared but then the keyboard input is handled fine.

@MelulekiDube commented on GitHub (May 28, 2019): @zadjii-msft This is with ssh.exe. With wsl the issue is the screen is not cleared but then the keyboard input is handled fine.
claunia commented 2026-01-30 22:23:55 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 28, 2019):

I'm going to say that there's a 99% chance then that this belongs in PowerShell/Win32-OpenSSH instead then.

Does this only repro in the Windows Terminal, or does this repro from a standard console window too? (try opening cmd.exe or powershell.exe, then launching ssh.exe)

@zadjii-msft commented on GitHub (May 28, 2019): I'm going to say that there's a 99% chance then that this belongs in [PowerShell/Win32-OpenSSH](https://github.com/PowerShell/Win32-OpenSSH/issues) instead then. Does this only repro in the Windows Terminal, or does this repro from a standard console window too? (try opening cmd.exe or powershell.exe, then launching ssh.exe)
claunia commented 2026-01-30 22:23:56 +00:00
Author
Owner
Copy Link

@MelulekiDube commented on GitHub (May 28, 2019):

@zadjii-msft The standard console window has the issue with not clearing the screen as well but the input is handled fine as well. As shown below:
image

Powershell, on the other hand, results in both screen not being cleared and the reaction to keyboard input being anomalous. Find below the output from PowerShell:
image

@MelulekiDube commented on GitHub (May 28, 2019): @zadjii-msft The standard console window has the issue with not clearing the screen as well but the input is handled fine as well. As shown below: ![image](https://user-images.githubusercontent.com/24409733/58489214-19739600-816b-11e9-8360-2117d0c4ce95.png) Powershell, on the other hand, results in both screen not being cleared and the reaction to keyboard input being anomalous. Find below the output from PowerShell: ![image](https://user-images.githubusercontent.com/24409733/58489386-7ec78700-816b-11e9-9e4d-c3f2bfee4422.png)
claunia commented 2026-01-30 22:23:56 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (May 28, 2019):

This looks like a standard case of what happens when the remote application has requested a specific terminal mode and been terminated without resetting it to default. In the vim case specifically, there’s nothing we can do about that!

@DHowett-MSFT commented on GitHub (May 28, 2019): This looks like a standard case of what happens when the remote application has requested a specific terminal mode and been terminated without resetting it to default. In the vim case specifically, there’s nothing we can do about that!
claunia commented 2026-01-30 22:23:56 +00:00
Author
Owner
Copy Link

@MelulekiDube commented on GitHub (May 28, 2019):

@DHowett-MSFT understood. I guess the issue with the keyboard is caused by vim open vim aswell as this is not reproducable when it was not open.
Thanks for the feedback.

@MelulekiDube commented on GitHub (May 28, 2019): @DHowett-MSFT understood. I guess the issue with the keyboard is caused by vim open vim aswell as this is not reproducable when it was not open. Thanks for the feedback.
claunia commented 2026-01-30 22:23:56 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (May 28, 2019):

This seems to have been answered.

@DHowett-MSFT commented on GitHub (May 28, 2019): This seems to have been answered.
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 Area-Input Issue-Question Product-Terminal 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#1371
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?