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

VS Code always get the first keyboard layout for shortcuts and screencast #114592

Closed
alexhausen opened this issue Jan 19, 2021 · 2 comments
Closed

Comments

@alexhausen
Copy link

Version: 1.52.1
Commit: ea3859d
Date: 2020-12-16T16:32:10.090Z
Electron: 9.3.5
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Ubuntu 20.04.1 LTS (Linux x64 5.8.0-38-generic)
Gnome: 3.36.8, X11

Also tested on version 1.53.0-insider with the same result.

Steps to Reproduce:

  1. Have 2 keyboard layouts configured on Linux, the first should be non-US,eg Portuguese (Brazil), the second one should be English (US).
  2. Select the second keyboard layout "en"
  3. Open VSCode and execute both Developer: Toggle Screencast Mode and Developer: Toggle Keyboard Shortcuts Troubleshooting
  4. Open a new file and type the key Ctrl+\ on your keyboard

Expected result:
Screencast bar displays Ctrl+\ and command Go to bracket is executed.

Actual result:
Screencast bar displays Ctrl+] and command Indent Line is executed, rendering the tab character (or spaces).

Keyboard Shortcuts Troubleshooting output when pressing Ctrl+\:

[2021-01-19 16:53:37.225] [renderer1] [info] [KeybindingService]: / Received  keydown event - modifiers: [ctrl], code: ControlLeft, keyCode: 17, key: Control
[2021-01-19 16:53:37.225] [renderer1] [info] [KeybindingService]: | Converted keydown event - modifiers: [ctrl], code: ControlLeft, keyCode: 5 ('Ctrl')
[2021-01-19 16:53:37.225] [renderer1] [info] [KeybindingService]: \ Keyboard event cannot be dispatched.
[2021-01-19 16:53:37.405] [renderer1] [info] [KeybindingService]: | Resolving ctrl+[Backslash]
[2021-01-19 16:53:37.406] [renderer1] [info] [KeybindingService]: \ From 1 keybinding entries, matched editor.action.indentLines, when: editorTextFocus && !editorReadonly, source: built-in.
[2021-01-19 16:53:37.407] [renderer1] [info] [KeybindingService]: / Received  keydown event - modifiers: [ctrl], code: Backslash, keyCode: 220, key: \
[2021-01-19 16:53:37.407] [renderer1] [info] [KeybindingService]: | Converted keydown event - modifiers: [ctrl], code: Backslash, keyCode: 88 ('\')
[2021-01-19 16:53:37.407] [renderer1] [info] [KeybindingService]: | Resolving ctrl+[Backslash]
[2021-01-19 16:53:37.408] [renderer1] [info] [KeybindingService]: \ From 1 keybinding entries, matched editor.action.indentLines, when: editorTextFocus && !editorReadonly, source: built-in.
  • Note: it may be easier to reproduce: pressing ; key renders ; character correctly but displays character ç in screencast bar.

Keyboard Shortcuts Troubleshooting output when pressing ;:

[2021-01-19 16:42:08.779] [renderer1] [info] [KeybindingService]: | Resolving [Semicolon]
[2021-01-19 16:42:08.779] [renderer1] [info] [KeybindingService]: \ No keybinding entries.
[2021-01-19 16:42:08.780] [renderer1] [info] [KeybindingService]: / Received  keydown event - modifiers: [], code: Semicolon, keyCode: 186, key: ;
[2021-01-19 16:42:08.780] [renderer1] [info] [KeybindingService]: | Converted keydown event - modifiers: [], code: Semicolon, keyCode: 80 (';')
[2021-01-19 16:42:08.781] [renderer1] [info] [KeybindingService]: | Resolving [Semicolon]
[2021-01-19 16:42:08.781] [renderer1] [info] [KeybindingService]: \ No keybinding entries.
  • Workaround: changing layout order on Gnome (first "en" then "pt") fixes the shortcut behavior.

vscode-1611087520082

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

@vscodebot
Copy link

vscodebot bot commented Jan 19, 2021

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

@alexdima
Copy link
Member

Duplicate of #24166

@alexdima alexdima marked this as a duplicate of #24166 Jan 20, 2021
@github-actions github-actions bot locked and limited conversation to collaborators Mar 6, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants