VsCode keeps typing like the key has not been released

This is Fedora 43, KDE, Wayland.

When taking an action in VsCode that opens a file or switches to a tab, (like ctrl+tab), sometimes the newly focused editor tab keeps typing the same key, like I have not released it.

I have re-installed Fedora, from Fedora KDE to Fedora Kinoite, and still have the problem.

I found some other reports of keyboard press/release irregularities in Fedora 43, but found no solution.

This happens with VsCode flatpak, installed inside a distrobox, and directly layered in the host.

Any help with a workaround that can fix this would be appreciated

I’ve had this occur with ydotool once. It’s quite a stretch, but perhaps check that its service is disabled for you. However, considering that it reproduces after a reinstallation, I’d check that you’re not synchronising a broken profile.

1 Like

Thanks. I don’t have ydotool. Switched to X11 and it seems like I don’t have the problem. Still would love to be able to fix/work-around and go back to Wayland

1 Like

Facing the same issue.
This KDE issue must be related

Update: found out that disabling GPU has the same effect as switching to X11: set
"disable-hardware-acceleration": true
in argv.json (ctrl+shift+P → configure runtime arguments)

I’m having a similar issue. It’s always the “tab” key that gets repeated. The trigger may have something to do with window switching or tab switching (both of which may involve pressing the tab-key). f43 KDE, not a vscode user. It happens often in firefox, and I’ve also seen it in meld. Pressing “Escape” always breaks the tab-flood.

Have you tried setting the “Virtual Keyboard” to “None”? I did this about 10 minutes ago, and have not had the issue since. I noticed that the setting reverts back to “Plasma Keyboard” when I re-open the settings, even though I pressed “Apply”. It seems to have a positive effect nonetheless.

1 Like

Which input method do you have selected as “Virtual Keyboard” in KDE System Settings?

I’m able to reproduce this issue with Plasma Keyboard. However IBus works just fine!

Thanks @the-rza . This seems to be the solution.
Due to the random nature of the problem, I need to work more to get more confidence, but sharing here as others might face the same problem.