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

WSL tmux screen scrambled when powershell.exe stderr redirected #14231

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

Originally created by @wedaly on GitHub (Jun 15, 2021).

Windows Terminal version (or Windows build number)

1.8.1521.0

Other Software

WSL2
Ubuntu 20.04
tmux 3.0a
powershell.exe (major: 5, minor: 1, build: 19041, revision: 1023)

Steps to reproduce

In Windows Terminal under WSL2 Ubuntu 20.04:

  1. Start a new tmux session: tmux new -s default
  2. Run powershell.exe Write-Host 'hello' 2> /dev/null
  3. Type: Ctrl-B, then :split-window -h to split the tmux window.
  4. The display is garbled (see screenshot below).

After closing and opening Windows terminal, the display returns to normal. I found that I needed to exit and start a new tmux session to reproduce the issue.

The issue occurs ONLY when redirecting stderr from powershell.exe. If I remove the redirection, the issue doesn't happen.

Expected Behavior

Tmux displays two panes with a separator, and "hello world" from powershell.exe is displayed in the left pane. It should look like this:

image

Actual Behavior

Tmux display is garbled (see screenshot) until closing and reopening Windows Terminal.

image

Originally created by @wedaly on GitHub (Jun 15, 2021). ### Windows Terminal version (or Windows build number) 1.8.1521.0 ### Other Software WSL2 Ubuntu 20.04 tmux 3.0a powershell.exe (major: 5, minor: 1, build: 19041, revision: 1023) ### Steps to reproduce In Windows Terminal under WSL2 Ubuntu 20.04: 1. Start a new tmux session: `tmux new -s default` 2. Run `powershell.exe Write-Host 'hello' 2> /dev/null` 3. Type: Ctrl-B, then `:split-window -h` to split the tmux window. 4. The display is garbled (see screenshot below). After closing and opening Windows terminal, the display returns to normal. I found that I needed to exit and start a new tmux session to reproduce the issue. The issue occurs ONLY when redirecting stderr from powershell.exe. If I remove the redirection, the issue doesn't happen. ### Expected Behavior Tmux displays two panes with a separator, and "hello world" from powershell.exe is displayed in the left pane. It should look like this: ![image](https://user-images.githubusercontent.com/2948394/121993928-30d54a00-cd59-11eb-83c1-bc842fa44ead.png) ### Actual Behavior Tmux display is garbled (see screenshot) until closing and reopening Windows Terminal. ![image](https://user-images.githubusercontent.com/2948394/121993873-18652f80-cd59-11eb-8a07-b57a005b8713.png)
claunia added the Resolution-ExternalNeeds-Tag-Fix labels 2026-01-31 04:04:30 +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 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#14231
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?