Summary: | Virtual keyboard stopped working since the last update, wayland | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Keziolio <keziolio123> |
Component: | virtual-keyboard | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | alan90000, benjamin.hennion, bennorton, xaver.hugl |
Priority: | NOR | ||
Version: | 5.19.0 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 5.19.4 |
Description
Keziolio
2020-06-09 22:59:52 UTC
Having the same problem on latest OpenSUSE Tumbleweed since 5.19.0, on 5.19.1 now and still a problem. In Wayland, the virtual keyboard comes up but as soon as you touch it, it closes, it's seems almost like it thinks your touching the desktop instead of the keyboard. In X11 qtvirtualkeyboard works fine. An additional problem that occurs that might help figure out the problem, When I enable using the virtual keyboard, and then change and apply anything in System Settings, the Application Menu when activated on My panel shows a very zoomed and stretched portion of some part of the screen across whole screen, instead of the menu, once I touch anything it goes back to the regular view. To get a working Application Menu back, I just need to disable the virtual keyboard. But I need to reboot to stop it happening again on re-enabling the virtual keyboard. Same problem, on 5.19.2. Same issue as https://bugs.kde.org/show_bug.cgi?id=423834. Seems to be actually due to the update from Qt 5.14.2 to Qt 5.15.0. It works well on Neon (wayland) with plasma-desktop 5.19.3, plasma-framework 5.72.0 and Qt 5.14.2 (booted from a live usb key, then into a wayland session). It does not work on Arch Linux with plasma-desktop 5.18.5, plasma-framework 5.70.1 and Qt 5.15.0 (nor with the latest updates 5.19.3/5.72.0/5.15.0). Updating to 5.19.4 fixed it for me. See also https://kde.org/announcements/plasma-5.19.3-5.19.4-changelog or https://invent.kde.org/plasma/kwin/commit/030cf0c57f4478f78c115962f4e15b0bf42600fe *** Bug 423834 has been marked as a duplicate of this bug. *** |