Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invisible command output in second monitor scaled differently #12793

Closed
servel333 opened this issue Mar 30, 2022 · 8 comments
Closed

Invisible command output in second monitor scaled differently #12793

servel333 opened this issue Mar 30, 2022 · 8 comments
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@servel333
Copy link

servel333 commented 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

@servel333 servel333 added the Issue-Bug It either shouldn't be doing this or needs an investigation. label Mar 30, 2022
@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Mar 30, 2022
@zadjii-msft
Copy link
Member

zadjii-msft commented 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

@servel333
Copy link
Author

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.

@DHowett
Copy link
Member

DHowett commented 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 😄

@servel333
Copy link
Author

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.

@zdavidsen
Copy link

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

@jessey-git
Copy link

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)

@zadjii-msft
Copy link
Member

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

/dup #11214

@ghost
Copy link

ghost commented 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 ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Apr 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

5 participants