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.

Sign up for GitHub

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

Jump to bottom

windows terminal no response when rdp dissconnect and reconnect #13152

Closed
SquallATF opened this issue May 24, 2022 · 4 comments
Closed

windows terminal no response when rdp dissconnect and reconnect #13152

SquallATF opened this issue May 24, 2022 · 4 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

@SquallATF
Copy link

Windows Terminal version

1.1210983.0

Windows build number

10.0.22621.0

Other Software

No response

Steps to reproduce

run some long text out put program with remote desktop(I'm run visual studio layout here), and disconnect remote desktop, and reconnect. The windows terminal window will no response.

Expected Behavior

No response

Actual Behavior

图片
@SquallATF SquallATF added the Issue-Bug It either shouldn't be doing this or needs an investigation. label May 24, 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 May 24, 2022
@zadjii-msft
Copy link
Member

This looks like #12607 to me. Do you happen to have an Nvidia graphics card/?

@ghost ghost added the Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something label May 24, 2022
@SquallATF
Copy link
Author

yes, I have an Nvidia graphics card, I think it is same to #12607

@ghost ghost added Needs-Attention The core contributors need to come back around and look at this ASAP. and removed Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something labels May 25, 2022
@zadjii-msft
Copy link
Member

Cool, thanks for following up!

/dup #12607

@zadjii-msft zadjii-msft closed this as not planned Won't fix, can't repro, duplicate, stale May 25, 2022
@ghost
Copy link

ghost commented May 25, 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 closed this as completed May 25, 2022
@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 Needs-Attention The core contributors need to come back around and look at this ASAP. labels May 25, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
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
Milestone
No milestone
Development

No branches or pull requests
2 participants
@SquallATF @zadjii-msft