Hmm, so I tried this today and I don’t seem to be able to reproduce it. Let’s take it step by step.
- I installed a clean F38 KDE into a virtual machine and fully updated it.
- On first login, there seems to be no accessibility menu that would allow me to trigger a virtual keyboard.
- After logging in, I can go to System Settings → Accessibility, there’s no virtual keyboard either.
- But I can go to System Settings → Input devices → Virtual Keyboard, and there’s None (default) and Maliit.
- If I enable Maliit, nothing happens. I don’t get a virtual keyboard when I click into a text field (Plasma, KWrite, etc).
- I create
~/.config/plasma-workspace/env/immodule_temp_fix.sh
as instructed in your workaround, reboot. - On login screen, there’s still no option to invoke a virtual keyboard, nor it pops up automatically (which makes sense, the workaround was done just for the user session).
- After logging in, the virtual keyboard still doesn’t pop up in text fields (Plasma, KWrite). I have no idea how to trigger it. In Plasma bottom right corner, there’s Input Method icon, but after clicking on it, it just says “On screen keyboard deactivated” (or “activated” when I click again), nothing happens.
I’m confused. First of all, why is the virtual keyboard not working at all? And second, what is your target use case? How does it help you to have a virtual keyboard in the user session when the login screen seems to have no support for it? Do you use it as an accessibility option or only when running KDE on a mobile device?