https://bugs.kde.org/show_bug.cgi?id=510454
Bug ID: 510454
Summary: Incorrect keyboard layout of Maliit keyboard in X11 or
Wine apps
Classification: Plasma
Product: kwin
Version First unspecified
Reported In:
Platform: Ubuntu
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: virtual-keyboard
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
SUMMARY
Maliit virtual keyboard produces incorrect character mappings in X11/XWayland
applications (e.g., "." outputs ":" instead).
STEPS TO REPRODUCE
1. Launch an X11 application through XWayland (e.g., xterm)
2. Activate Maliit virtual keyboard
3. Type characters such as "." or other punctuation/symbols
OBSERVED RESULT
Wrong characters are produced. For example, typing "." outputs ":" instead.
Multiple other character substitutions occur. Testing with "xev" confirms
incorrect characters are being sent at the X11 protocol level.
EXPECTED RESULT
Maliit virtual keyboard should produce the same correct character mappings in
X11/XWayland applications as it does in native Wayland applications and as
physical keyboards do in all applications.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Ubuntu 24.04
KDE Plasma Version: 5.27.12
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.13
Session: Wayland
ADDITIONAL INFORMATION
- Physical keyboard input works correctly in all applications (both Wayland and
X11)
- Maliit keyboard works correctly in native Wayland applications
- Issue only affects Maliit keyboard when used with X11/XWayland applications
- Problem appears to be in the Wayland-to-X11 translation layer within KWin's
XWayland handling
- Maliit-Developers directed us towards kwin:
https://github.com/maliit/keyboard/issues/253
We're using this framework in this scope:
https://www.galaxus.ch/en/page/mini-but-mighty-the-mini-computers-getting-the-job-done-22049
We're currently lacking the skills to debug this issue in reasonable technical
depth. We're willing to provide debugging logs, configuration files, or any
other diagnostic information needed. Additionally, we're prepared to finance a
bounty to help prioritize fixing this issue upstream (for the community - not
(just) for us). Please advise on next steps for both debugging assistance and
bounty arrangement.
--
You are receiving this mail because:
You are watching all bug changes.
