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 sometimes sends Ctrl+C to the shell when moving tabs #23452

New Issue
Closed
opened 2026-01-31 08:42:41 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 08:42:41 +00:00
Owner
Copy Link

Originally created by @apromenschenkel on GitHub (Jul 17, 2025).

Windows Terminal version

1.22.11141.0

Windows build number

10.0.22621.5472

Other Software

I use terminal with WSL 2.3.26.0 almost exclusively. I'm not sure if this effects other shells such as PowerShell or Command Prompt.

Steps to reproduce

This is an intermittent issue. It is unknown what causes it to occur or not.

Click and hold a Terminal tab and then either drag it to a different position in the tab bar, or drag it away from the tab bar to detach it in its own window.

Expected Behavior

Rearranging tabs shouldn't send any text input to the shell.

Actual Behavior

Occasionally, rearranging tabs causes a Ctrl+C character to be sent to the shell. This is particularly problematic in bash if the shell is running an application, because this sends SIGINT to the running program and causes it to stop.

A screen capture of this occuring:

https://github.com/user-attachments/assets/e1cc049e-229f-4715-8c56-0b3f686e2e3f

Originally created by @apromenschenkel on GitHub (Jul 17, 2025). ### Windows Terminal version 1.22.11141.0 ### Windows build number 10.0.22621.5472 ### Other Software I use terminal with WSL 2.3.26.0 almost exclusively. I'm not sure if this effects other shells such as PowerShell or Command Prompt. ### Steps to reproduce This is an intermittent issue. It is unknown what causes it to occur or not. Click and hold a Terminal tab and then either drag it to a different position in the tab bar, or drag it away from the tab bar to detach it in its own window. ### Expected Behavior Rearranging tabs shouldn't send any text input to the shell. ### Actual Behavior Occasionally, rearranging tabs causes a Ctrl+C character to be sent to the shell. This is particularly problematic in bash if the shell is running an application, because this sends SIGINT to the running program and causes it to stop. A screen capture of this occuring: https://github.com/user-attachments/assets/e1cc049e-229f-4715-8c56-0b3f686e2e3f
claunia added the Needs-TriageIssue-BugNeeds-Author-FeedbackNo-Recent-Activity labels 2026-01-31 08:42:42 +00:00
claunia commented 2026-01-31 08:42:43 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Jul 21, 2025):

Interesting... That's not something I've experienced before. Or even seen before.

It may be helpful to record a trace like this: https://github.com/microsoft/terminal/wiki/Troubleshooting-Tips#capturing-a-debug-etl-trace

@lhecker commented on GitHub (Jul 21, 2025): Interesting... That's not something I've experienced before. Or even seen before. It may be helpful to record a trace like this: https://github.com/microsoft/terminal/wiki/Troubleshooting-Tips#capturing-a-debug-etl-trace
claunia commented 2026-01-31 08:42:43 +00:00
Author
Owner
Copy Link

@apromenschenkel commented on GitHub (Jul 21, 2025):

Thanks for your response. Here is a terminal tap of the issue (in both text and screenshot form), as well as the output of the linux "script" command in the file "term2". I am unable to capture an ETL trace because this is occurring on a work machine where I do not have the ability to start an elevated terminal. I can try and recreate this issue on a personal machine if these files don't provide enough information.

term2.txt
Terminal Debug Tap.txt
Image

@apromenschenkel commented on GitHub (Jul 21, 2025): Thanks for your response. Here is a terminal tap of the issue (in both text and screenshot form), as well as the output of the linux "script" command in the file "term2". I am unable to capture an ETL trace because this is occurring on a work machine where I do not have the ability to start an elevated terminal. I can try and recreate this issue on a personal machine if these files don't provide enough information. [term2.txt](https://github.com/user-attachments/files/21351521/term2.txt) [Terminal Debug Tap.txt](https://github.com/user-attachments/files/21351520/Terminal.Debug.Tap.txt) <img width="1915" height="405" alt="Image" src="https://github.com/user-attachments/assets/66844c3e-76eb-4832-9d24-17b29e847f9a" />
claunia commented 2026-01-31 08:42:44 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Aug 6, 2025):

Alas, the debug tap does make it look like there's a ^C coming from somewhere. It looks like a legitimate keyboard event... but we are absolutely not emitting it.

Expanding the search a little bit, do you have any software that might try to interact with the clipboard (such as, by trying to force a copy with Ctrl+C) on every new window?

@DHowett commented on GitHub (Aug 6, 2025): Alas, the debug tap does make it look like there's a `^C` coming from _somewhere_. It looks like a legitimate keyboard event... but we are absolutely not emitting it. Expanding the search a little bit, do you have any software that might try to interact with the _clipboard_ (such as, by trying to force a copy with <kbd>Ctrl+C</kbd>) on every new window?
claunia commented 2026-01-31 08:42:44 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Aug 6, 2025):

(Or other window management software?)

@DHowett commented on GitHub (Aug 6, 2025): (Or other window management software?)
claunia commented 2026-01-31 08:42:44 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (Aug 10, 2025):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@microsoft-github-policy-service[bot] commented on GitHub (Aug 10, 2025): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**. <!-- Policy app identification https://img.shields.io/static/v1?label=PullRequestIssueManagement. -->
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-Bug Needs-Author-Feedback Needs-Triage No-Recent-Activity
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#23452
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?