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

Ctrl key can be stuck in Windows Terminal #14343

Closed
devlie opened this issue Nov 4, 2022 · 4 comments
Closed

Ctrl key can be stuck in Windows Terminal #14343

devlie opened this issue Nov 4, 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

@devlie
Copy link
Member

devlie commented Nov 4, 2022

Windows Terminal version

1.15.2875.0

Windows build number

10.0.25231.1000

Other Software

No response

Steps to reproduce

I don't have concrete repro steps. I'm just using running cmd.exe inside Windows Terminal Preview as usual.

Expected Behavior

Ctrl key is not stuck.

Actual Behavior

After some times, Ctrl key will be stuck for a particular tab. I usually find out when hitting Backspace would delete the whole word even though I'm not pressing down Ctrl key, or typing some alphabets would produce something like ^A

I'm positive the problem is scoped to a Terminal tab:

  • If I open a new tab, the issue doesn't persist.
  • The problem doesn't repro on Windows Run dialog (WIN+R) while issue is happening.
@devlie devlie added Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Nov 4, 2022
@lhecker
Copy link
Member

lhecker commented Nov 5, 2022

Wow that sounds eerily similar to #14338, which was submitted just hours ago.

@zadjii-msft
Copy link
Member

I'm gonna go out on a limb and guess that this is the same root cause as #14345. We'll tentatively call this a dupe for now, push out a hotfix, and if that release doesn't fix this, we can reopen. Thanks!

/dup #14129

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

ghost commented Nov 7, 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 Nov 7, 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 labels Nov 7, 2022
@devlie
Copy link
Member Author

devlie commented Feb 14, 2023

@zadjii-msft I'm still reproing this issue on WT Preview 1.17.1023. That build should have the fix for this issue, right?

@devlie devlie mentioned this issue Feb 24, 2023
Closed
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
3 participants
@lhecker @zadjii-msft @devlie