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

Terminal force closes with ssh session and multiple screens #3385

Closed
ihor-sviziev opened this issue Oct 31, 2019 · 3 comments
Closed

Terminal force closes with ssh session and multiple screens #3385

ihor-sviziev opened this issue Oct 31, 2019 · 3 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@ihor-sviziev
Copy link

ihor-sviziev commented Oct 31, 2019

Environment

Windows build number: Microsoft Windows [Version 10.0.18362.449]
Windows Terminal version (if applicable): 0.6.2951.0

Link to Feedback: https://aka.ms/AA6f0m9

Prerequisites

  1. 3 monitors, 1st and 2nd -with Full HD resolution and 100% scaling, 3rd - 2550x1440 and 150% scaling
  2. Installed Ubuntu 18.04 WSL

Steps to reproduce

  1. Open WSL Ubuntu 18.04 in Windows Terminal, keep it in screen 1 or 2 (with 100% scaling)
  2. connect to via ssh to any server (tried to connect to Amazon Linux)
  3. Move Windows Terminal to 3rd screen (with 150% scaling)
  4. Wait 3 seconds
  5. Move Windows Terminal to 2nd screen (with 100% scaling)

Expected behavior

Loading indicator is shown, in few seconds terminal is closed

Actual behavior

Terminal should continue working without any issues

Note: on "Ubuntu 18.04 LTS" app this issue isn't reproducing

@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 Oct 31, 2019
@benfulton
Copy link

I can reproduce this with two monitors and without connecting via ssh. I have Ubuntu 18.04 as my default terminal.

@DHowett-MSFT
Copy link
Contributor

This sounds like a /dupe of #3303. Thanks!

@ghost
Copy link

ghost commented Oct 31, 2019

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 closed this as completed Oct 31, 2019
@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 Oct 31, 2019
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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

3 participants