https://bugs.kde.org/show_bug.cgi?id=521857
Bug ID: 521857
Summary: Letter keydown events not delivered to Chromium
clients on Wayland since KWin 6.7 (modifiers still
fire)
Classification: Plasma
Product: kwin
Version First 6.7.0
Reported In:
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: wayland-generic
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
Created attachment 193431
--> https://bugs.kde.org/attachment.cgi?id=193431&action=edit
Reproducer
Summary
After updating to Plasma 6.7.0, Chromium-based browsers (Google Chrome
149.0.7827.155 confirmed) stop receiving keydown events for letter keys on any
focused text input when running natively on Wayland. Modifier keys (Shift,
Ctrl, Alt) still produce keydown. The corresponding input events still fire and
text is inserted into the field — only keydown is suppressed.
This breaks every web app that depends on KeyboardEvent.code for letter keys:
code editors, typing tutors with layout emulation, games. As a concrete case,
keybr.com Practice mode with "Emulate layout" enabled becomes unusable.
The same Chrome version on the same machine in Plasma 6.6.x worked correctly
the day before the upgrade.
Steps to reproduce
Plasma 6.7.0 (KWin 6.7.0), Wayland session.
Google Chrome 149+ launched with defaults (i.e. native Wayland via Ozone,
WaylandTextInputV3 enabled, which is the upstream default since Chromium commit
e48954bd, April 2025).
Open the attached keydown-test.html (or visit any page with a focused
<textarea>/<input>).
Click into the input to focus it.
Press a letter key (e.g. a).
Expected
Both keydown and input events fire. Counter for keydown increments.
Actual
Only input event fires. keydown counter stays at 0 for letters. Pressing Shift,
Ctrl, Backspace, Tab, arrow keys correctly fires keydown.
Bisection
Same Chrome 149.0.7827.155, same hardware.
Before Plasma upgrade (KWin 6.6.x): keydown for letters fires normally.
After Plasma upgrade (KWin 6.7.0): keydown for letters suppressed.
So the regression sits on the KWin 6.7.0 side. Three suspect changes in that
release in the text-input / input-method code:
fc98b4bcbd80ba025994c2d31244d984a253ec66 — "Support Text Input 3.2"
5f2ef797d64ae8ad085025cbd827e383cc3a5b1d — "inputmethodcontext: Only report
enabled if input method is accepted"
bug 519924 — "Ensure correct ordering of keyboard events with input grabs"
Workarounds confirmed
--ozone-platform=x11 (forces Chrome to use XWayland): keydown fires normally.
This is what the user is on while waiting for a fix.
GTK_IM_MODULE= QT_IM_MODULE= XMODIFIERS= does NOT help — confirms it's not an
IME daemon, it's the Wayland text-input protocol path itself.
Environment
Distribution: Fedora 44 KDE (rolling)
Session type: Wayland ($XDG_SESSION_TYPE=wayland)
KDE Plasma: 6.7.0
KWin: 6.7.0
Google Chrome: 149.0.7827.155
No IME daemon active for English layout (no ibus / fcitx / fcitx5 processes)
Reproducer
Attached keydown-test.html is a single-file standalone page with four test
cards (hidden textarea, inputmode="none" textarea, contenteditable div, visible
textarea). All four exhibit the same behavior on Wayland under KWin 6.7.0:
keydown only for modifiers, input for letters.
--
You are receiving this mail because:
You are watching all bug changes.
