https://bugs.kde.org/show_bug.cgi?id=455080
old486wh...@gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |old486wh...@gmail.com
--- Comment #11 from old486wh...@gmail.com ---
So I'm in a similar boat.
Fedora 36 (wayland + KWIN used)
KDE Plasma 5.25.2
Framework 5.94
QT version 5.15.3
I find it amazing that no-one from KDE seems to care that an accessibility
requirement like a virtual keyboard is not working.
Alex - could you try checking your environment variables on a "konsole" (type
the following - without quotes - "set |grep MODULE").
Also, on that same window, try typing (again no quotes):
"QT_IM_MODULE=qtvirtualkeyboard kwrite"
On mine, I get an error message and the "maliit" keyboard flashes up.
The error is: "qt.qpa.wayland: qtvirtualkeyboard currently is not supported at
client-side, use QT_IM_MODULE=qtvirtualkeyboard at compositor-side."
I suspect that because "ibus" is set then the virtual keyboard isn't
appearing.....
Which is silly isn't it? ibus is purposely built to use an input method
mechanism, while force-setting it to ONLY virtualkeyboard is wrong for things
where you can plug in keyboards, or 2-in-1 laptops where the keyboard folds
away.
Even worse - where can I set the IM module variable on the compositor-side? do
I have to manually edit the "kwinrc" file? Other files?
I will try to take this further myself, but why is the virtual keyboard not
showing in ALL situations where it's enabled!? This is just bad user
experience!
--
You are receiving this mail because:
You are watching all bug changes.
