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

Mouse clic write stuff to terminal after being disconnected from remote #19504

New Issue
Closed
opened 2026-01-31 06:45:21 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 06:45:21 +00:00
Owner
Copy Link

Originally created by @4wk- on GitHub (Mar 7, 2023).

Windows Terminal version

1.16.10261.0

Windows build number

10.0.19045.2604

Other Software

No response

Steps to reproduce

  • Yesterday night, I had a multi windows setup on Windows Terminal, all running the Debian profile, and most of them were connected to a few remote Linux server using SSH.
  • On two windows, I used htop command to see live usage of server hardware (CPU, RAM, etc).
  • Then my computer went to sleep mode and lost internet connection.
  • On all the windows console connected to the remote server, I've got the usual message when getting disconnected client_loop: send disconnect: Broken pipe (I usually do a clear, and move on, but not this time)
  • Only on the 2 windows that were displaying the htop command I have an issue

Expected Behavior

I expect to get a full working console terminal on only windows.

Actual Behavior

But this time, only on the 2 windows that were displaying htop commands, I have a strange behavour of Windows Terminal:
=> Whenever I use my left click or right click on those windows, Windows beep and write to the console some stuff that appear to be the position of my mouse (because it changes whenever I move it then click).
For instance: X4#X4 or r2#r2 etc. Right click write the same kind of stuff but prefixed with ".

I ran exec bash --login to see if it was an issue with my Debian profile, but the issue with mouse click persists.
I didn't find a way to "restart" only those two windows of Windows Terminal to fix them.

Originally created by @4wk- on GitHub (Mar 7, 2023). ### Windows Terminal version 1.16.10261.0 ### Windows build number 10.0.19045.2604 ### Other Software _No response_ ### Steps to reproduce - Yesterday night, I had a multi windows setup on Windows Terminal, all running the Debian profile, and most of them were connected to a few remote Linux server using SSH. - On two windows, I used `htop` command to see live usage of server hardware (CPU, RAM, etc). - Then my computer went to sleep mode and lost internet connection. - On all the windows console connected to the remote server, I've got the usual message when getting disconnected `client_loop: send disconnect: Broken pipe` (I usually do a `clear`, and move on, but not this time) - Only on the 2 windows that were displaying the `htop` command I have an issue ### Expected Behavior I expect to get a full working console terminal on only windows. ### Actual Behavior But this time, only on the 2 windows that were displaying `htop` commands, I have a strange behavour of Windows Terminal: => Whenever I use my left click or right click on those windows, Windows beep and **write to the console some stuff that appear to be the position of my mouse** (because it changes whenever I move it then click). For instance: `X4#X4` or `r2#r2` etc. Right click write the same kind of stuff but prefixed with `"`. I ran `exec bash --login` to see if it was an issue with my Debian profile, but the issue with mouse click persists. I didn't find a way to "restart" only those two windows of Windows Terminal to fix them.
claunia added the Issue-QuestionNeeds-Tag-FixResolution-Answered labels 2026-01-31 06:45:22 +00:00
claunia commented 2026-01-31 06:45:23 +00:00
Author
Owner
Copy Link

@4wk- commented on GitHub (Mar 7, 2023):

Here is a screenshot.

  • in red: the previous display of htop command (OK). When getting disconnected, this is a normal behavour, the last stuff displayed stay on screen, but the prompt climb all the way to the top left.
  • in purple: the actual message from getting disconnected (OK)
  • in blue: all my left click and some right click, writing strange stuff to my console (KO)

windowsTerminalIssue

As stated before, I'm using Windows Terminal with a 6 split console, and this issue appear on only 2 of them.
Thank you for you help, and please let me know if you need more information or if I should test stuff.
I've search the opened issues but didn't find something similar (but to be honest, searching for "cursor" or "mouse click" etc is a very broad subject)

@4wk- commented on GitHub (Mar 7, 2023): Here is a screenshot. - in red: the previous display of `htop` command (OK). When getting disconnected, this is a normal behavour, the last stuff displayed stay on screen, but the prompt climb all the way to the top left. - in purple: the actual message from getting disconnected (OK) - in blue: all my left click and some right click, writing strange stuff to my console (KO) ![windowsTerminalIssue](https://user-images.githubusercontent.com/1439550/223365024-5732f696-e069-40eb-8e10-05bbf72e63e1.png) As stated before, I'm using Windows Terminal with a 6 split console, and this issue appear on only 2 of them. Thank you for you help, and please let me know if you need more information or if I should test stuff. I've search the opened issues but didn't find something similar (but to be honest, searching for "cursor" or "mouse click" etc is a very broad subject)
claunia commented 2026-01-31 06:45:23 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 7, 2023):

Basically, what happened here is that when your opened htop on the remote machine, it requested something called "mouse mode" from the Terminal. This causes mouse input to be sent as a string of characters like what you're seeing (but usually htop just reads them and never prints them to the screen). However, because ssh exited unexpectedly, htop never had a chance to cleanly exit mouse mode and return the Terminal to the normal state.

I believe a reset would fix this. If not, I can try and conjure up something more elaborate to manually reset each of the mouse modes.

See also: #6909, #6941

@zadjii-msft commented on GitHub (Mar 7, 2023): Basically, what happened here is that when your opened `htop` on the remote machine, it requested something called "mouse mode" from the Terminal. This causes mouse input to be sent as a string of characters like what you're seeing (but usually `htop` just reads them and never prints them to the screen). However, because `ssh` exited unexpectedly, `htop` never had a chance to cleanly exit mouse mode and return the Terminal to the normal state. I believe a `reset` would fix this. If not, I can try and conjure up something more elaborate to manually reset each of the mouse modes. See also: #6909, #6941
claunia commented 2026-01-31 06:45:23 +00:00
Author
Owner
Copy Link

@4wk- commented on GitHub (Mar 7, 2023):

@zadjii-msft Thanks for your quick reply, and explaining what is truely going on! That make sense. reset command indeed fixed the issue, so that's perfect. Sorry, I should have think of reset myself.
Thanks again! You can close this issue.

@4wk- commented on GitHub (Mar 7, 2023): @zadjii-msft Thanks for your quick reply, and explaining what is truely going on! That make sense. `reset` command indeed fixed the issue, so that's perfect. Sorry, I should have think of `reset` myself. Thanks again! You can close this issue.
claunia commented 2026-01-31 06:45:23 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Mar 7, 2023):

Thanks for following up!

@DHowett commented on GitHub (Mar 7, 2023): Thanks for following up!
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 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#19504
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?