caret, tick, backtick and diaeresis can't be written.

[lsmor]

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

• VS Code Version: 1.67.1
• OS Version: Ubuntu 20.04.4 LTS

Steps to Reproduce:

1. Configure your keyboard with Spanish layout
2. launch vscode with gtk input method xim. GTK_IM_MODULE="xim" code
3. try to write any of the following characters ^, `, ´, á,é,í,ó, ú, ü, etc...

The reason to use xim input method is due to (#48480 (comment)). launching vscode with ibus or using a different keyboard layout makes those character tp work fine, but then some keyboard shorcut stop working.

Also, it seems that this issue affects only vscode, since launching other gtk applications (such as gnome-calculator) with input method "xim" doesn't make those character to fail.

[alexdima]

@lsmor VS Code is built with Electron, which is built with Chromium. Could you please try launching Chromium and checking if input works in Chromium as expected?

[vscodenpa]

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.

Happy Coding!

[serranomorante]

So annoying! I'm also facing this with no avail.

[lsmor]

Sorry for not answering sooner.

@serranomorante follow this answer and try if it works. #48480 (comment)

In my case it didn't. I changed my input method globally. In ubuntu open "Language Support" and then set input method to XIM. Below, there is a capture (My system is in spanish)

@lsmor VS Code is built with Electron, which is built with Chromium. Could you please try launching Chromium and checking if input works in Chromium as expected?

Yes. Chromium's input work as expected in Brave and Discord, which AFAIK are both electron apps. Notice that the linked issue points out to a clash between Gnome shortcuts and vscode shortcuts. I don't know where the problem is.

[alexdima]

@lsmor Could you please also try configuring "keyboard.dispatch": "keyCode" and restarting VS Code. Does that help with the keyboard shortcuts?

[serranomorante]

Sorry for not answering sooner.

@serranomorante follow this answer and try if it works. #48480 (comment)

In my case it didn't. I changed my input method globally. In ubuntu open "Language Support" and then set input method to XIM. Below, there is a capture (My system is in spanish)

@lsmor VS Code is built with Electron, which is built with Chromium. Could you please try launching Chromium and checking if input works in Chromium as expected?

Yes. Chromium's input work as expected in Brave and Discord, which AFAIK are both electron apps. Notice that the linked issue points out to a clash between Gnome shortcuts and vscode shortcuts. I don't know where the problem is.

Hi. Thank you for the link. I had already tried that and it didn't work.
XIM is the only thing that works with the shortcut ctrl + shift + e but that causes the new issue you described.

[serranomorante]

@lsmor Could you please also try configuring "keyboard.dispatch": "keyCode" and restarting VS Code. Does that help with the keyboard shortcuts?

Also tried this, didn't work for me.

[lsmor]

@lsmor Could you please also try configuring "keyboard.dispatch": "keyCode" and restarting VS Code. Does that help with the keyboard shortcuts?

This didn't work. Below there is the log when typing the word "maná" (via "Toggle Keyboard Shortcut Troubleshooting"), which is typed KeyM-KeyA-KeyN-Quote-KeyA

As you can see it detectes the quote but not the second A.

[2022-08-03 16:41:29.223] [renderer1] [info] [KeybindingService]: / Received  keydown event - modifiers: [], code: KeyM, keyCode: 77, key: m
[2022-08-03 16:41:29.325] [renderer1] [info] [KeybindingService]: | Converted keydown event - modifiers: [], code: KeyM, keyCode: 43 ('M')
[2022-08-03 16:41:29.326] [renderer1] [info] [KeybindingService]: | Resolving [KeyM]
[2022-08-03 16:41:29.326] [renderer1] [info] [KeybindingService]: \ From 1 keybinding entries, no when clauses matched the context.
[2022-08-03 16:41:29.838] [renderer1] [info] [KeybindingService]: / Received  keydown event - modifiers: [], code: KeyA, keyCode: 65, key: a
[2022-08-03 16:41:29.839] [renderer1] [info] [KeybindingService]: | Converted keydown event - modifiers: [], code: KeyA, keyCode: 31 ('A')
[2022-08-03 16:41:29.839] [renderer1] [info] [KeybindingService]: | Resolving [KeyA]
[2022-08-03 16:41:29.840] [renderer1] [info] [KeybindingService]: \ From 1 keybinding entries, no when clauses matched the context.
[2022-08-03 16:41:30.710] [renderer1] [info] [KeybindingService]: / Received  keydown event - modifiers: [], code: KeyN, keyCode: 78, key: n
[2022-08-03 16:41:30.713] [renderer1] [info] [KeybindingService]: | Converted keydown event - modifiers: [], code: KeyN, keyCode: 44 ('N')
[2022-08-03 16:41:30.714] [renderer1] [info] [KeybindingService]: | Resolving [KeyN]
[2022-08-03 16:41:30.715] [renderer1] [info] [KeybindingService]: \ No keybinding entries.
[2022-08-03 16:41:31.386] [renderer1] [info] [KeybindingService]: / Received  keydown event - modifiers: [], code: Quote, keyCode: 222, key: Dead
[2022-08-03 16:41:31.388] [renderer1] [info] [KeybindingService]: | Converted keydown event - modifiers: [], code: Quote, keyCode: 90 (''')
[2022-08-03 16:41:31.389] [renderer1] [info] [KeybindingService]: | Resolving [Quote]
[2022-08-03 16:41:31.391] [renderer1] [info] [KeybindingService]: \ No keybinding entries.
[2022-08-03 16:41:31.613] [renderer1] [info] [KeybindingService]: / Received  keydown event - modifiers: [], code: , keyCode: 0, key: 
[2022-08-03 16:41:31.614] [renderer1] [info] [KeybindingService]: | Converted keydown event - modifiers: [], code: , keyCode: 0 ('unknown')
[2022-08-03 16:41:31.615] [renderer1] [info] [KeybindingService]: \ Keyboard event cannot be dispatched in keydown phase.

[serranomorante]

Not a solution but for now I will just continue using IBus instead of XIM as keyboard input method system and just replace ctrl+shift+e for another shortcut (ctrl+shift+a) in vscode. Even though this doesn't fix this particular issue, at least it would let me continue working with vscode for now.