https://bugs.kde.org/show_bug.cgi?id=522347
Bug ID: 522347
Summary: Plasma Login Manager: Virtual keyboard non-functional
and causes hardware keyboard input failure on Wayland
(6.7)
Classification: Plasma
Product: kwin
Version First 6.7.0
Reported In:
Platform: CachyOS
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: virtual-keyboard
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
Created attachment 193822
--> https://bugs.kde.org/attachment.cgi?id=193822&action=edit
system info and log
**Title:** Plasma Login Manager: Virtual keyboard non-functional and causes
hardware keyboard input failure on Wayland (6.7)
**Description:**
The virtual keyboard button appears on the Plasma Login Manager lock screen but
is non-functional. When attempting to enable it via environment variables, it
enters a rapid show/hide loop and disables hardware keyboard input, making it
impossible to log in.
**Environment:**
- **Distribution:** CachyOS (Arch Linux-based)
- **KDE Plasma Version:** 6.7.0
- **Display Server:** Wayland (XDG_SESSION_TYPE=wayland)
- **Login Manager:** Plasma Login Manager (default as of January 2026 ISO)
- **Session:** Plasmawayland
- **Virtual Keyboard Packages:**
- `plasma-keyboard 6.7.0-1.1`
- `qt6-virtualkeyboard 6.11.1-1.1`
- **Hardware:** Non-touchscreen device (standard laptop)
**Complete system info**:
https://paste.cachyos.org/p/03b6225.log
**Steps to Reproduce:**
1. Boot CachyOS with default KDE Plasma 6.7 on Wayland
2. Install plasma-keyboard package.
3. Lock the screen
4. Observe the virtual keyboard button on the lock screen
5. Click the virtual keyboard button → nothing happens (expected: keyboard
appears)
6. To enable virtual keyboard, attempt to set environment variables:
- Try: `export KWIN_IM_SHOW_ALWAYS=1` in
`~/.config/plasma-workspace/env/qtvirtualkeyboard.sh`; logout & login & lock
screen & click virtual keyboard button on lock screen → nothing happens
7. Try: `export QT_IM_MODULES=qtvirtualkeyboard` in
`/etc/environment.d/qtvirtualkeyboard.conf`
8. Reboot and return to login screen
9. Observe the virtual keyboard rapidly showing and hiding
10. Attempt to type password with hardware keyboard → **no input is
registered**
11. System becomes locked (unable to authenticate)
**Expected Behavior:**
- Virtual keyboard button on lock screen should activate the on-screen keyboard
when clicked
- Hardware keyboard input should remain functional at all times
- No rapid show/hide loops
**Actual Behavior:**
- Virtual keyboard button does nothing when clicked
- Setting `QT_IM_MODULES=qtvirtualkeyboard` globally causes the keyboard to
enter a rapid show/hide loop on the login screen
- During the show/hide loop, hardware keyboard input is completely disabled
- User cannot log in without removing the environment variable configuration
**Relevant Logs:**
>From `journalctl` when `plasma-keyboard` is active:
```
plasma-keyboard[49604]: qtvirtualkeyboard currently is not supported at
client-side, use QT_IM_MODULES=qtvirtualkeyboard at compositor-side.
plasma-keyboard[49604]: Failed to register with host portal
QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID:
Connection already associated with an application ID")
plasmashell[49986]: QDBusConnection: couldn't handle call to
VirtualKeyboardModeChanged, no slot matched
plasmashell[49986]: Could not find slot Osd::VirtualKeyboardModeChanged
```
Additional errors when `QT_IM_MODULES=qtvirtualkeyboard` is set globally:
- Rapid cycling of `VirtualKeyboardModeChanged` DBus signals
- Hardware keyboard input events are not processed by the login manager
**Workarounds Attempted:**
1. ✗ `KWIN_IM_SHOW_ALWAYS=1` in
`~/.config/plasma-workspace/env/qtvirtualkeyboard.sh` → No effect
2. ✗ `QT_IM_MODULES=qtvirtualkeyboard` in
`/etc/environment.d/qtvirtualkeyboard.conf` → Breaks hardware keyboard input
3. ✓ **Current workaround:** Use hardware keyboard to type password (virtual
keyboard remains unavailable)
**Possible Root Causes:**
1. Plasma Login Manager's Wayland compositor is not properly delegating input
focus when the virtual keyboard is enabled
2. The DBus interface for `VirtualKeyboardModeChanged` is missing or misnamed
in the lock screen context
3. Global `QT_IM_MODULES` setting conflicts with Plasma Login Manager's
internal input method handling on Wayland
4. Virtual keyboard support in Plasma Login Manager may not be fully
implemented for non-touchscreen devices
**Additional Notes:**
- Virtual keyboard **works correctly** inside the Wayland session (after login)
- The virtual keyboard button is **visually present** on the lock screen,
suggesting partial implementation
- This appears to be specific to **Plasma Login Manager on Wayland**; may not
affect SDDM or X11 sessions
- Affects users on non-touchscreen devices who need accessibility features
--
You are receiving this mail because:
You are watching all bug changes.
