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

Windows Terminal becomes unusable after running gradle in WSL #17234

New Issue
Closed
opened 2026-01-31 05:36:11 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 05:36:11 +00:00
Owner
Copy Link

Originally created by @mjsztainbok on GitHub (Apr 13, 2022).

Windows Terminal version

1.11.3471.0

Windows build number

10.0.19043.0

Other Software

gradle 7.4

Steps to reproduce

Do a gradle build which produces errors

Expected Behavior

The terminal window operates correctly and can accept keyboard input

Actual Behavior

Sometimes after the gradle build the tab stops responding and it doesn't respond to keypresses. You can still scroll the tab though.
It also shows still shows the cursor on focus. Pressing Ctrl-L to reset the UI in the shell doesn't do anything.

This is how the window looks:
image

Originally created by @mjsztainbok on GitHub (Apr 13, 2022). ### Windows Terminal version 1.11.3471.0 ### Windows build number 10.0.19043.0 ### Other Software gradle 7.4 ### Steps to reproduce Do a gradle build which produces errors ### Expected Behavior The terminal window operates correctly and can accept keyboard input ### Actual Behavior Sometimes after the gradle build the tab stops responding and it doesn't respond to keypresses. You can still scroll the tab though. It also shows still shows the cursor on focus. Pressing Ctrl-L to reset the UI in the shell doesn't do anything. This is how the window looks: ![image](https://user-images.githubusercontent.com/67809434/163069656-dbb9e34c-db3f-48fe-8750-53e4ac8b65b9.png)
claunia commented 2026-01-31 05:36:13 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 13, 2022):

Hmm. That's sure weird. I honestly don't know what would cause that... Like, I don't think there's anything that gradle can emit to prevent the Terminal from sending more input. I suppose it's possible that gradle left the tty in a bad state, where input is no longer echoed. That's maybe something. You might be able to still enter reset or stty sane in this state, and hopefully the shell still receives those?

How are you running gradle? As gradel.exe? Via WSL? Or via msys2/cygwin/etc?

@zadjii-msft commented on GitHub (Apr 13, 2022): Hmm. That's sure weird. I honestly don't know what would cause that... Like, I don't think there's anything that gradle can emit to prevent the Terminal from sending more input. I suppose it's possible that gradle left the tty in a bad state, where input is no longer echoed. That's maybe something. You might be able to still enter `reset` or `stty sane` in this state, and hopefully the shell still receives those? How are you running gradle? As gradel.exe? Via WSL? Or via msys2/cygwin/etc?
claunia commented 2026-01-31 05:36:13 +00:00
Author
Owner
Copy Link

@mjsztainbok commented on GitHub (Apr 13, 2022):

I'm running the Linux version of gradle in Ubuntu on WSL:

------------------------------------------------------------
Gradle 7.4
------------------------------------------------------------

Build time:   2022-02-08 09:58:38 UTC
Revision:     f0d9291c04b90b59445041eaa75b2ee744162586

Kotlin:       1.5.31
Groovy:       3.0.9
Ant:          Apache Ant(TM) version 1.10.11 compiled on July 10 2021
JVM:          11.0.14.1 (Ubuntu 11.0.14.1+1-Ubuntu-0ubuntu1.20.04)
OS:           Linux 5.10.60.1-microsoft-standard-WSL2 amd64

The shell doesn't get any inputs when it's like this so no commands work. It's not a case of it not echoing the input. It's not receiving the input at all.

@mjsztainbok commented on GitHub (Apr 13, 2022): I'm running the Linux version of gradle in Ubuntu on WSL: ``` ------------------------------------------------------------ Gradle 7.4 ------------------------------------------------------------ Build time: 2022-02-08 09:58:38 UTC Revision: f0d9291c04b90b59445041eaa75b2ee744162586 Kotlin: 1.5.31 Groovy: 3.0.9 Ant: Apache Ant(TM) version 1.10.11 compiled on July 10 2021 JVM: 11.0.14.1 (Ubuntu 11.0.14.1+1-Ubuntu-0ubuntu1.20.04) OS: Linux 5.10.60.1-microsoft-standard-WSL2 amd64 ``` The shell doesn't get any inputs when it's like this so no commands work. It's not a case of it not echoing the input. It's not receiving the input at all.
claunia commented 2026-01-31 05:36:13 +00:00
Author
Owner
Copy Link

@mjsztainbok commented on GitHub (Jun 10, 2022):

Actually it's not just gradle where this happens. It seems to occur after any failing commands in the shell in WSL

@mjsztainbok commented on GitHub (Jun 10, 2022): Actually it's not just gradle where this happens. It seems to occur after any failing commands in the shell in WSL
claunia commented 2026-01-31 05:36:13 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 15, 2022):

Honestly, I have no idea what's going on here. Does this repro in a vintage console window, as well as in a Terminal window? Do you have a minimal repro of a command that causes this (smaller than just "sometimes after a gradle build"/? Does the content of the tab "reflow" if you resize the terminal window to be a smaller width? (that might help ID if the Terminal control itself is hung, or it's something else behind the scenes that's hung.

@zadjii-msft commented on GitHub (Aug 15, 2022): Honestly, I have no idea what's going on here. Does this repro in a vintage console window, as well as in a Terminal window? Do you have a minimal repro of a command that causes this (smaller than just "sometimes after a gradle build"/? Does the content of the tab "reflow" if you resize the terminal window to be a smaller width? (that might help ID if the Terminal control itself is hung, or it's something else behind the scenes that's hung.
claunia commented 2026-01-31 05:36:14 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 19, 2022):

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.

@ghost commented on GitHub (Aug 19, 2022): 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**.
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-Tag-Fix 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#17234
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?