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

Ctrl key prevents further keyboard or mouse input #244786

Open
adettenb opened this issue Mar 26, 2025 · 0 comments
Open

Ctrl key prevents further keyboard or mouse input #244786

adettenb opened this issue Mar 26, 2025 · 0 comments
Assignees
Labels
stale Issues that have not been triaged in an appropriate amount of time triage-needed

Comments

@adettenb
Copy link

Does this issue occur when all extensions are disabled?: Yes

  • VS Code Version: 1.98.2 (ddc367e)
  • OS Version: 24H2 (OS Build 26100.3476)

Often when pressing Ctrl to perform hotkey actions, or when Ctrl is tapped independently, VSCode becomes unresponsive to keyboard or mouse input. The app doesn't freeze, since the text caret is still blinking, but it stops reacting to user input. This causes most notibly hotkeys which include the Ctrl key to fail, and makes it difficult to edit documents.

This issue is flaky, occasionally it'll reproduce many times in succession, while other times it'll work fine. Whatever condition is causing this to begin failing is unclear.

While experiencing this issue, opening the Windows Start Menu allows VSCode to continue accepting input, but tapping the Ctrl key afterwards will very often cause the issue to reproduce again.

Steps to Reproduce:

  1. Open Visual Studio Code
  2. Open any document
  3. Tap the left Ctrl key
  4. Notice VSCode ignores further keyboard or mouse input is ignored, but the text caret still blinks.
  5. Tap the Windows key to open the Start Menu
  6. Notice VSCode again responds to keyboard and mouse input
  7. Repeat steps 3 onward to continue reproducing the bug
@vs-code-engineering vs-code-engineering bot added the stale Issues that have not been triaged in an appropriate amount of time label Apr 2, 2025
@lszomoru lszomoru removed their assignment Apr 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Issues that have not been triaged in an appropriate amount of time triage-needed
Projects
None yet
Development

No branches or pull requests

3 participants