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

Command prompt goes black after awaking from sleep #1090

New Issue
Closed
opened 2026-01-30 22:16:15 +00:00 by claunia · 4 comments
claunia commented 2026-01-30 22:16:15 +00:00
Owner
Copy Link

Originally created by @miniksa on GitHub (May 14, 2019).

Ported out from customer feedback bug MSFT:21308307.

I haven't managed to reproduce or investigate this at all yet.

I have 2 open command prompts (regular, and admin powershell). I locked my computer last night, and it went to sleep automatically. After waking from sleep this morning, both terminals were showing black screens instead of the text that should be on them. Scrolling the window seems to cause a repaint and fixes the issue.

This also seems to affect 3rd party terminal apps as well (e.g. Terminus).

Originally created by @miniksa on GitHub (May 14, 2019). Ported out from customer feedback bug MSFT:21308307. I haven't managed to reproduce or investigate this at all yet. > I have 2 open command prompts (regular, and admin powershell). I locked my computer last night, and it went to sleep automatically. After waking from sleep this morning, both terminals were showing black screens instead of the text that should be on them. Scrolling the window seems to cause a repaint and fixes the issue. > > This also seems to affect 3rd party terminal apps as well (e.g. Terminus).
claunia commented 2026-01-30 22:16:16 +00:00
Author
Owner
Copy Link

@iKlsR commented on GitHub (Aug 14, 2019):

Roughly the same, mine crashes if my PC goes to sleep, the display turns off or I lock it.

@iKlsR commented on GitHub (Aug 14, 2019): Roughly the same, mine crashes if my PC goes to sleep, the display turns off or I lock it.
claunia commented 2026-01-30 22:16:17 +00:00
Author
Owner
Copy Link

@YoungElPaso commented on GitHub (May 16, 2020):

Similar, twice now WT has crashed on sleep - everything else resumes. I should note, I assumed it was WSL2 that crashed, but I think it's just the sessions in WT (using Ubuntu 18.04). The reason I suspect that is because other processes such as Docker are still up and running, which I didn't expect to see.

@YoungElPaso commented on GitHub (May 16, 2020): Similar, twice now WT has crashed on sleep - everything else resumes. I should note, I assumed it was WSL2 that crashed, but I think it's just the sessions in WT (using Ubuntu 18.04). The reason I suspect that is because other processes such as Docker are still up and running, which I didn't expect to see.
claunia commented 2026-01-30 22:16:17 +00:00
Author
Owner
Copy Link

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

Hey so we ported this out of the OS issue tracker like, 3 years ago. It was specifically referencing the vintage console window, not the Terminal window. That being said, we haven't gotten more reports of this for the console since then. There also wasn't more info in the original issue (internally) which we could really use to investigate.

I'm inclined to close this out. Niksa can veto if he wants.

@zadjii-msft commented on GitHub (Aug 16, 2022): Hey so we ported this out of the OS issue tracker like, 3 years ago. It was specifically referencing the vintage console window, not the Terminal window. That being said, we haven't gotten more reports of this for the _console_ since then. There also wasn't more info in the original issue (internally) which we could really use to investigate. I'm inclined to close this out. Niksa can veto if he wants.
claunia commented 2026-01-30 22:16:17 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 20, 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 20, 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 Area-Rendering Issue-Bug Needs-Author-Feedback Needs-Repro No-Recent-Activity Product-Conhost
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#1090
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?