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

Invisible command output in second monitor scaled differently #17125

New Issue
Closed
opened 2026-01-31 05:32:50 +00:00 by claunia · 8 comments
claunia commented 2026-01-31 05:32:50 +00:00
Owner
Copy Link

Originally created by @servel333 on GitHub (Mar 30, 2022).

Windows Terminal version

1.11.3471.0

Windows build number

10.0.19044.1526

Other Software

No response

Steps to reproduce

  • Have a computer with two different scaling factors (for example, 4k laptop and old monitor)
    • My setup is a Microsoft Surface Book 3 with an old monitor connected through a hub and adapter
  • Enable WSL2
  • Install Ubuntu in WSL2
  • Open Windows Terminal
  • Move the terminal window to the lower-ratio monitor
  • try ls and other commands a few times
    • It's possible there must be colored output for this to reproduce. I often use git status with colors enabled and see this issue.

Expected Behavior

Command output (stdout) is visible and colored as expected.

Actual Behavior

Command output (stdout) is sometimes invisible.

Some additional notes

  • Selecting the invisible space with the mouse makes the text visible one line at a time
  • Moving the Windows Terminal window across the monitor boundary causes the text to become visible.
  • Changing the scaling factor on the external monitor to different than back will temporarily resolve this issue.
  • Resizing the Windows Terminal window (click and drag edge) will temporarily resolve this issue.
  • The issue returns if the Windows Terminal window is dragged across monitor boundaries and more output is generated.
  • See also This superuser.com Question for details and screenshots. Also not comments under the main question.
  • It's possible this is related to https://github.com/microsoft/terminal/issues/6210
Originally created by @servel333 on GitHub (Mar 30, 2022). ### Windows Terminal version 1.11.3471.0 ### Windows build number 10.0.19044.1526 ### Other Software _No response_ ### Steps to reproduce - Have a computer with two different scaling factors (for example, 4k laptop and old monitor) - My setup is a Microsoft Surface Book 3 with an old monitor connected through a hub and adapter - Enable WSL2 - Install Ubuntu in WSL2 - Open Windows Terminal - Move the terminal window to the lower-ratio monitor - try `ls` and other commands a few times - It's possible there must be colored output for this to reproduce. I often use `git status` with colors enabled and see this issue. ### Expected Behavior Command output (stdout) is visible and colored as expected. ### Actual Behavior Command output (stdout) is sometimes invisible. ### Some additional notes - Selecting the invisible space with the mouse makes the text visible one line at a time - Moving the Windows Terminal window across the monitor boundary causes the text to become visible. - Changing the scaling factor on the external monitor to different than back will temporarily resolve this issue. - Resizing the Windows Terminal window (click and drag edge) will temporarily resolve this issue. - The issue returns if the Windows Terminal window is dragged across monitor boundaries and more output is generated. - See also [This superuser.com Question](https://superuser.com/questions/1713554/how-do-i-fix-command-output-in-terminal-is-invisible-on-external-monitor) for details and screenshots. Also not comments under the main question. - It's possible this is related to https://github.com/microsoft/terminal/issues/6210
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 05:32:50 +00:00
claunia commented 2026-01-31 05:32:51 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 30, 2022):

This might be better in 1.12 or 1.13, there was a weird scaling issue that was solved in the latest release. I'd doubt it, I think that had more to do with the resizing of the swapchainpanel itself (not invalidating), but worth a shot to check out.

#11317

Ah shiz, we didn't backport that one. ... Wait, did we? 2327e26

@zadjii-msft commented on GitHub (Mar 30, 2022): This might be better in 1.12 or 1.13, there was a weird scaling issue that was solved in the latest release. I'd doubt it, I think that had more to do with the resizing of the swapchainpanel itself (not invalidating), but worth a shot to check out. #11317 Ah shiz, we didn't backport that one. ... Wait, did we? 2327e26
claunia commented 2026-01-31 05:32:51 +00:00
Author
Owner
Copy Link

@servel333 commented on GitHub (Mar 30, 2022):

I'll see if I can grab a newer version and test, if one is publicly available.

It's definitely a weird bug. I wouldn't expect screen scaling to matter to the terminal.

@servel333 commented on GitHub (Mar 30, 2022): I'll see if I can grab a newer version and test, if one is publicly available. It's definitely a weird bug. I wouldn't expect screen scaling to matter to the terminal.
claunia commented 2026-01-31 05:32:52 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Mar 30, 2022):

The fix is unfortunately not yet out -- however, screen scaling matters to the Terminal because it's gotta get that good good grid of text into pixels somehow 😄

@DHowett commented on GitHub (Mar 30, 2022): The fix is unfortunately not yet out -- however, screen scaling matters to the Terminal because it's gotta get that good good grid of text into pixels _somehow_ :smile:
claunia commented 2026-01-31 05:32:52 +00:00
Author
Owner
Copy Link

@servel333 commented on GitHub (Mar 31, 2022):

I guess I assumed the operating system would handle application scaling?

Regardless, when the new version comes out, I will test it. I can't guarantee I will remember, so if you happen to, your welcome to @mention me here again.

@servel333 commented on GitHub (Mar 31, 2022): I guess I assumed the operating system would handle application scaling? Regardless, when the new version comes out, I will test it. I can't guarantee I will remember, so if you happen to, your welcome to @mention me here again.
claunia commented 2026-01-31 05:32:52 +00:00
Author
Owner
Copy Link

@zdavidsen commented on GitHub (Mar 31, 2022):

I've seen this (or something similar) a couple times recently as well. I can't reproduce it on demand, but every time I've noticed it has been when moving the terminal from my 4k/150% monitor to the 1080p/100% monitor.

I think it's different than the main issue in #11317 for several reasons:

  • 11317 only happened (for me at least) when moving from lower -> higher scaling. Command output disappearing is happening when moving the opposite direction (from higher -> lower scaling)
  • I've seen the output disappear in the middle of the terminal, with previous prompts displaying correctly both above and below the invisible output.

So apparently it's much easier to reproduce than I thought it was, I just don't normally scroll that much so it was easy to miss

InvisibleTerminalOutput

@zdavidsen commented on GitHub (Mar 31, 2022): I've seen this (or something similar) a couple times recently as well. ~I can't reproduce it on demand,~ but every time I've noticed it has been when moving the terminal from my 4k/150% monitor to the 1080p/100% monitor. I _think_ it's different than the main issue in #11317 for several reasons: - 11317 only happened (for me at least) when moving from lower -> higher scaling. Command output disappearing is happening when moving the opposite direction (from higher -> lower scaling) - I've seen the output disappear in the middle of the terminal, with previous prompts displaying correctly both above and below the invisible output. So apparently it's much easier to reproduce than I thought it was, I just don't normally scroll that much so it was easy to miss ![InvisibleTerminalOutput](https://user-images.githubusercontent.com/22267435/161124714-d72f6971-47b3-4655-9348-35a2b7b911b1.gif)
claunia commented 2026-01-31 05:32:52 +00:00
Author
Owner
Copy Link

@jessey-git commented on GitHub (Apr 1, 2022):

There is also #11214 that is still active that deals with moving between monitors at different scale (and when remoting into other machines with different resolutions)

@jessey-git commented on GitHub (Apr 1, 2022): There is also #11214 that is still active that deals with moving between monitors at different scale (and when remoting into other machines with different resolutions)
claunia commented 2026-01-31 05:32:52 +00:00
Author
Owner
Copy Link

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

Yea, this does look just like #11214. Let's combine discussion in there.

/dup #11214

@zadjii-msft commented on GitHub (Apr 8, 2022): Yea, this does look just like #11214. Let's combine discussion in there. /dup #11214
claunia commented 2026-01-31 05:32:52 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Apr 8, 2022):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Apr 8, 2022): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
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 Resolution-Duplicate
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#17125
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?