This is too great not to share. Wayland devs hate this trick! I’ll copy what I did from the bug report.
As a workaround you can use https://github.com/Supreeeme/extest to make Onboard work. Compile it as a 64 bit library and launch onboard with
env LD_PRELOAD=/usr/lib64/libextest.so onboardIf you want to use it with KDE you can add
X-KDE-Wayland-VirtualKeyboard=trueto its desktop-file.
I used kwin rules to get rid of window decorations and have it always on top without stealing focus. If someone knows how to make all other windows smaller when it’s active that would be great.
Only problem remaining is that sometimes the keys get stuck on touch input. At least on my Steam Deck on OpenSUSE.
The problems with Maliit are that it lacks special keys like Ctrl, Alt, Tab, Esq, F1-F12, etc. And you cannot invoke it by yourself to type in XWayland applications or others which don’t pull up the keyboard by themselves.
The Gnome keyboard seems to be better in that regard but I couldn’t even find its name to pull it up outside of Gnome.
Yes you can
How?
I mean, I got a different solution by now, but would be nice to know for the future.
Cool. They didnt ask for a fully-featured keyboard, they asked for a wayland-compatible onscreen keyboard.
In that case please state which Wayland support it has. That’s the beauty of standards, there are so many to choose from. And in the case of Wayland keyboards you have to know which one the keyboard and which the compositor supports, making it extra easy for the user.