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

Can't send SIGQUIT ( crtl + \ ) to WSL (Debian) #8518

New Issue
Open
opened 2026-01-31 01:31:27 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 01:31:27 +00:00
Owner
Copy Link

Originally created by @zimbobway on GitHub (May 23, 2020).

Environment

Win32NT 10.0.18362.0 Microsoft Windows NT 10.0.18362.0

Windows Terminal
Version: 1.0.1401.0

Debian running on WSL
uname -r
4.4.0-18362-Microsoft

Related info:
https://github.com/microsoft/WSL/issues/169

Steps to reproduce

Run Terminal
Open new Debian Window
run ping 127.0.0.1
(wait for 3 ping responses)
send SIGQUIT ( crtl + \ )

Expected behavior

Ping statistics summary is displayed, while ping command continues. For instance:

PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.028 ms
64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.188 ms
64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=0.033 ms
3/3 packets, 0% loss, min/avg/ewma/max = 0.028/0.083/0.046/0.188 ms
64 bytes from 127.0.0.1: icmp_seq=4 ttl=64 time=0.032 ms
64 bytes from 127.0.0.1: icmp_seq=5 ttl=64 time=0.030 ms

Actual behavior

^\ is printed at the beginning of next ping sequence line and no statistics summary is displayed, ping command continues. For instance:

PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.
64 bytes from 127.0.0.1: icmp_seq=1 ttl=128 time=0.084 ms
64 bytes from 127.0.0.1: icmp_seq=2 ttl=128 time=0.100 ms
64 bytes from 127.0.0.1: icmp_seq=3 ttl=128 time=0.106 ms
^\64 bytes from 127.0.0.1: icmp_seq=4 ttl=128 time=0.108 ms
64 bytes from 127.0.0.1: icmp_seq=5 ttl=128 time=0.107 ms

Originally created by @zimbobway on GitHub (May 23, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- 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. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment Win32NT 10.0.18362.0 Microsoft Windows NT 10.0.18362.0 Windows Terminal Version: 1.0.1401.0 Debian running on WSL uname -r 4.4.0-18362-Microsoft Related info: https://github.com/microsoft/WSL/issues/169 # Steps to reproduce Run Terminal Open new Debian Window run ping 127.0.0.1 (wait for 3 ping responses) send SIGQUIT ( crtl + \ ) # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> Ping statistics summary is displayed, while ping command continues. For instance: PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data. 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.028 ms 64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.188 ms 64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=0.033 ms 3/3 packets, 0% loss, min/avg/ewma/max = 0.028/0.083/0.046/0.188 ms 64 bytes from 127.0.0.1: icmp_seq=4 ttl=64 time=0.032 ms 64 bytes from 127.0.0.1: icmp_seq=5 ttl=64 time=0.030 ms # Actual behavior ^\ is printed at the beginning of next ping sequence line and no statistics summary is displayed, ping command continues. For instance: PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data. 64 bytes from 127.0.0.1: icmp_seq=1 ttl=128 time=0.084 ms 64 bytes from 127.0.0.1: icmp_seq=2 ttl=128 time=0.100 ms 64 bytes from 127.0.0.1: icmp_seq=3 ttl=128 time=0.106 ms ^\64 bytes from 127.0.0.1: icmp_seq=4 ttl=128 time=0.108 ms 64 bytes from 127.0.0.1: icmp_seq=5 ttl=128 time=0.107 ms <!-- What's actually happening? -->
claunia added the Product-WSLResolution-ExternalNeeds-Tag-Fix labels 2026-01-31 01:31:28 +00:00
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 Product-WSL 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#8518
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?