Problem: When switching tabs or opening a file using Ctrl + P shortcut then pressing Enter after switching to the file the Enter key prompt gets stuck creating new lines in the file. Same with Ctrl + Tab, the tab key prompt leaks into the switched tab’s file and gets stuck creating tabulations (4 spaces).
It only seems to happen in Electron based apps tested in VSCode, VsCodium, Windsurf.
The issue doesn’t seem appear under X11.
What I tried:
Launching any of those apps with --enable-features=UseOzonePlatform --ozone-platform=wayland args - no change.
setting keyboard.dispatch to keyCode - no changes.
Operating System: Arch Linux
KDE Plasma Version: 6.6.2
KDE Frameworks Version: 6.23.0
Qt Version: 6.10.2
Kernel Version: 6.19.6-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-10610U CPU @ 1.80GHz
Memory: 32 GiB of RAM (31.1 GiB usable)
Graphics Processor: Intel® UHD Graphics
Same issue here with Ctrl+P or Ctrl+Tab to switch editor tabs in VSCode. It happens on almost every tab switch. I have to press another key like Esc to stop the continued key presses filling my editor, then perform multiple undos to revert the changes.
I first noticed this behavior about a week ago.
Tried your suggestions of running with code –ozone-platform=x11 and that is having promising results so far.
Exactly, same exact issue. It’s most definitely tied to one of the recent plasma updates and is NOT something to do with VSCode itself because as I mentioned it happens in VSCode clones as well. For now using the args to run it under x11 seems to resolve the issue.
Electron based apps seem to be always having issues under Wayland
man!!, I did everything to fix this bug. Now Im in an entirely different os, i had dualbooted windows and fedora before and now i bluescreened windows , my first fedora is overshadowed by new fedora, i configured everything and still got this bug.
for some reason, chat gpt decided to give me this solution after changing everything.
You can replace code with any other VSCode based code editor like windsurf-flags.conf, vscodium-flags.conf.
This is better because it’s not only restricted to the desktop launcher, it also works if you run any of these apps from the terminal eliminating the need of manually adding the argument
Just encountered this issue on a separate machine with a different KDE Plasma version, different VSCode version, and different GPUs, so I thought I’d share the extra data point:
Hi! You might me onto something, even if everything works fine with the args in the *-flags.conf file. Setting Virtual Keyboard to None seems to have fixed the issue? Can’t really be sure since I kinda forgot about the issue and had updated plasma too, iirc. So could be many things but yes I just set my virtual keyboard to None which is what I had before by default, I’m on a clean arch setup where Plasma Keyboard wasn’t even installed and I did install it for some experiment thing I did I am not really sure if that’s related and if the bug started at the moment I installed and set plasma keyboard as the virtual keyboard. In any case, Thanks!