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

Unable to enter symbols via keyboard layout shifting in Wayland #160262

Closed
rikedyp opened this issue Sep 7, 2022 · 2 comments
Closed

Unable to enter symbols via keyboard layout shifting in Wayland #160262

rikedyp opened this issue Sep 7, 2022 · 2 comments
Assignees
Labels
linux Issues with VS Code on Linux

Comments

@rikedyp
Copy link

rikedyp commented Sep 7, 2022

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

Version: 1.71.0
Commit: 784b017
Date: 2022-09-01T07:25:10.472Z
Electron: 19.0.12
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: 10.2.154.15-electron.0
OS: Linux x64 5.19.6-200.fc36.x86_64
Sandboxed: No

OS: Fedora Linux 35 (Workstation Edition)
GNOME: 42.4

Steps to Reproduce:

  1. Install Gnome Tweaks
  2. In Tweaks, go to Keyboard & Mouse and click Additional Layout Options
  3. Under Switching to another layout select a shifting key (e.g. Right Alt (while pressed) - note this issue does not occur if a non-(while pressed) option is selected
  4. In the normal Gnome Settings, under Keyboard add another Input Source - it is best to use one with a different script, such as Russian, so that the problem is more obvious
  5. Open a program such as gnome-text-editor
  6. Notice that typing normally produces Latin characters (if you are using a Latin layout such as English language ones), and the holding AltGr (Right Alt, or whatever was chosen in step 3) and typing produces other characters (Cyrillic if using Russian).
  7. Open VSCode
  8. Try step 6 and notice that alternate characters (Cyrillic) are not produced while AltGr is held

The closest-looking issue I've found is #127932 but setting "keyboard.dispatch": "keyCode" does not seem to help.

@rikedyp
Copy link
Author

rikedyp commented Sep 7, 2022

There is a workaround. The problem goes away with:

code --enable-features=UseOzonePlatform --ozone-platform=wayland

I would prefer if this was enabled by default.

Related issue: electron/electron#28436

@deepak1556
Copy link
Collaborator

We cannot flip the default backend to wayland until the runtime makes the relevant changes, refs #134612. I recommend using the CLI flag to use the wayland backend. Also you do not need the flag --enable-features=UseOzonePlatform. Instead use the following code --ozone-platform=wayland

@github-actions github-actions bot locked and limited conversation to collaborators Oct 23, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
linux Issues with VS Code on Linux
Projects
None yet
Development

No branches or pull requests

4 participants