For some months now, I don't remember exactly when, I started encountering a really annoying bug: in my browser (Vivaldi), The Delete key on the numeric keypad stopped workingIt really annoyed me, because it's the key I always used to delete. I had no choice but to use the one above it, next to Insert. My curiosity led me to discover that this also happens in other Chromium-based browsers, like Brave.
More recently I have discovered the real problem: in some configurations, the Delete key on the numeric keypad It will stop working if Wayland is used.The bug will be experienced in any software based on Chromium. For example, in Visual Studio Code and Electron applications. Knowing that the problem arises when Chromium and Wayland are combined, we can now take action.
Does 'Supr' not work for you on Wayland and Chromium?
The first thing we need to do to verify that the error is as described in this article is to open a program with the error in an X11 window. For example, for Vivaldi in X11, we would open a terminal and type:
vivaldi –ozone-platform=x11
The above command, which should be written with Vivaldi closed, will open it as it would in X11. If the key works, we have already identified and partially solved the problem. The permanent solution requires patience and waiting for the developers to fix the issue.
In KDE, a temporary solution might be to open the "Menu Editor" app, find the problematic application, and in the "Command Line Arguments" section add –ozone-platform=x11It's possible that these arguments disappear each time the application is updated, and the solution would be to add them back.
Another option is to create a .desktop file in ~ / .local / share / applicationsBut this is more complicated.
What is lost?
When an app X11 runs on Wayland (via XWayland) usually works almost the same, but there are differences because Wayland manages things like the keyboard, focus, and scaling itself and then "translates" them to X11. In that step, small errors can appear: some special keys don't arrive the same, the clipboard or focus may behave differently, and scaling or screenshots may have problems.
My recommendation is to check if it's worthwhile in your specific case. Personally, I don't miss anything, so I've added the arguments to Vivaldi and Visual Studio Code to be able to use a key I press instinctively.