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

build 18298.1000 console breaks with WSL #484

New Issue
Closed
opened 2026-01-30 21:53:25 +00:00 by claunia · 5 comments
claunia commented 2026-01-30 21:53:25 +00:00
Owner
Copy Link

Originally created by @nicferrier on GitHub (Dec 12, 2018).

Originally assigned to: @zadjii-msft on GitHub.

  • Your Windows build number: (Type ver at a Windows Command Prompt)

Microsoft Windows [Version 10.0.18298.1000]

  • What you're doing and what's happening: (Copy&paste specific commands and their output, or include screen shots)

For example:

  • start WSL,
  • vi ~/.bashrc
  • quit vi

console no longer prints anything.

It can be reset by doing ls -la.

If you have emacs installed:

  • emacs -nw
  • screen looks wierd
  • quit emacs

console now has a red background.

The same sort of thing happens with htop, less and I guess any terminal app using colors?

  • What's wrong / what should be happening instead:

curses apps should be working.

Originally created by @nicferrier on GitHub (Dec 12, 2018). Originally assigned to: @zadjii-msft on GitHub. * Your Windows build number: (Type `ver` at a Windows Command Prompt) Microsoft Windows [Version 10.0.18298.1000] * What you're doing and what's happening: (Copy&paste specific commands and their output, or include screen shots) For example: - start WSL, - vi ~/.bashrc - quit vi console no longer prints anything. It can be reset by doing ls -la. If you have emacs installed: - emacs -nw - screen looks wierd - quit emacs console now has a red background. The same sort of thing happens with htop, less and I guess any terminal app using colors? * What's wrong / what should be happening instead: curses apps should be working.
claunia added the Product-ConhostResolution-Fix-Available labels 2026-01-30 21:53:25 +00:00
claunia commented 2026-01-30 21:53:26 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Dec 12, 2018):

Huh, I was sure that @bitcrazed was supposed to file this...

This is already known, and fixed in internal branches. The fix should be out to Insider's soontm

@zadjii-msft commented on GitHub (Dec 12, 2018): Huh, I was sure that @bitcrazed was supposed to file this... This is already known, and fixed in internal branches. The fix should be out to Insider's soon<sup>tm</sup>
claunia commented 2026-01-30 21:53:26 +00:00
Author
Owner
Copy Link

@bitcrazed commented on GitHub (Dec 13, 2018):

I LITERALLY just came here to file this bug and found that @nicferrier got there first! :) NICE! 🍾

Another repro:

From Cmd/PowerShell, if I run:

C:\>wsl man ls

The man page appears and everything is fine. Then when I hit q to exit, it drops back to the Cmd/PowerShell, but the foreground color is the same as the background color:

C:\>wsl man ls
 
                  _

Only if I execute color to reset the colors can I see the text again. This didn’t used to happen. It happens with any kind of interactive command in WSL.

@bitcrazed commented on GitHub (Dec 13, 2018): I LITERALLY just came here to file this bug and found that @nicferrier got there first! :) NICE! 🍾 Another repro: From Cmd/PowerShell, if I run: ``` C:\>wsl man ls ``` The man page appears and everything is fine. Then when I hit <kbd>q</kbd> to exit, it drops back to the Cmd/PowerShell, but the foreground color is the same as the background color: ``` C:\>wsl man ls _ ``` Only if I execute `color` to reset the colors can I see the text again. This didn’t used to happen. It happens with any kind of interactive command in WSL.
claunia commented 2026-01-30 21:53:26 +00:00
Author
Owner
Copy Link

@oising commented on GitHub (Dec 13, 2018):

Yeah, just noticed this too on 18298, which took about eight attempts to install on top of 18290. Sheesh - is this the reward I get for my persistence? 🤣

@oising commented on GitHub (Dec 13, 2018): Yeah, just noticed this too on 18298, which took about eight attempts to install on top of 18290. Sheesh - is this the reward I get for my persistence? 🤣
claunia commented 2026-01-30 21:53:27 +00:00
Author
Owner
Copy Link

@nicferrier commented on GitHub (Dec 27, 2018):

Yeah, just noticed this too on 18298, which took about eight attempts to install on top of 18290. Sheesh - is this the reward I get for my persistence? 🤣

Frustrating isn't it? But Microsoft are slowly fixing the console stuff which has been broken for ever (35 years?) so I try to sniff a candle or have a bath or something to reduce my frustration.

@nicferrier commented on GitHub (Dec 27, 2018): > > > Yeah, just noticed this too on 18298, which took about eight attempts to install on top of 18290. Sheesh - is this the reward I get for my persistence? 🤣 Frustrating isn't it? But Microsoft are slowly fixing the console stuff which has been broken for ever (35 years?) so I try to sniff a candle or have a bath or something to reduce my frustration.
claunia commented 2026-01-30 21:53:27 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jan 10, 2019):

This should work as of 18309 or 18312.

@DHowett-MSFT commented on GitHub (Jan 10, 2019): This should work as of 18309 or 18312.
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 Product-Conhost Resolution-Fix-Available
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#484
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?