| Summary: | Implement the Wayland virtual-keyboard-unstable-v1 protocols to support tools like wtype | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Relma <amulyamo> |
| Component: | virtual-keyboard | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | CONFIRMED --- | ||
| Severity: | task | CC: | john.kizer, nate, tobias.bora, xaver.hugl |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Relma
2024-12-22 09:16:26 UTC
Hi - just to verify, does the information at https://github.com/Hoverth/wayland-virtual-keyboards?tab=readme-ov-file#other-tips , around adding a .desktop file parameter to enable support, apply in the case you're describing? What application do I have to put `X-KDE-Wayland-VirtualKeyboard=true` into?? I'm confused; wtype is a command-line tool It may require creating a .desktop file for wtype with that parameter, if one isn't already placed into /usr/share/applications/. The .desktop file for Maliit, which should be at /usr/share/applications/com.github.maliit.keyboard.desktop , might be a guide there. Once that is in place, it should be selectable in System Settings > Keyboard > Virtual Keyboard. wtype is not a virtual keyboard; i don't think that applies in this case Related to this github issue: https://github.com/atx/wtype/issues/45 The Virtual keyboard protocol to support is zwp_virtual_keyboard_v1, outlined here: https://wayland.app/protocols/virtual-keyboard-unstable-v1#compositor-support As you can see, KDE's KWin does not support this. Thanks for specifying the link! *** Bug 502882 has been marked as a duplicate of this bug. *** |