protonscr

[Linux/X11] Keyboard input not working in Steam Overlay and Big Picture with Russian layout (XKB)

steamopen Big PictureoverlayDistro Family: Arch
ValveSoftware/steam-for-linux#12316 · opened 2025-09-12 by Wolfen113 · updated 2026-08-14 · 7 comments · github
WWolfen113 2025-09-12 github

Translated and formatted via GPT4

System Information

  • OS: Arch Linux x86_64
  • Kernel: Linux 6.16.5-arch1-1
  • DE: Cinnamon 6.4.10 (X11, Muffin WM)
  • GPU: NVIDIA GeForce GTX 1660 Ti (driver 580.82.07, Open driver)
  • Steam client version: steam-runtime_1.0.20250616.139563
  • Locale: ru_RU.UTF-8
  • Input: XKB (no ibus/fcitx running)
  • Packages: ~1400 (pacman)

The issue

When using Russian keyboard layout (XKB), keyboard input does not work inside:

  • Steam Overlay (Shift+Tab)
  • Big Picture mode

Text fields (chat, notes, search, etc.) do not register key presses on Russian layout.
Switching back to English layout fixes the issue.
Outside of Overlay/Big Picture (normal Steam client windows), input works fine.

This issue looks similar to how some games ignore non-English layouts under XKB.

For several years now, with client updates, the problem has disappeared for a short time, then returned again.

Steps to reproduce

  1. Launch Steam on Arch Linux (X11, Cinnamon).
  2. Switch keyboard layout to Russian (setxkbmap us,ru).
  3. Open Overlay (Shift+Tab) or Big Picture.
  4. Try typing in chat or search field → no input is registered.

Expected behavior

Text input should work with Russian (and other non-English) layouts in Overlay and Big Picture.

Tried workarounds

  • Running Steam with different input variables:
    • SDL_IM_MODULE=xim QT_IM_MODULE=xim XMODIFIERS=@im=none steam
    • LANG=ru_RU.UTF-8 LC_CTYPE=ru_RU.UTF-8 steam
  • Configuring layouts via setxkbmap.
  • No IBus/Fcitx is running.

None of these fixed the issue.

Additional info

This problem appeared before, disappeared after a Steam update, but recently reappeared with the latest client.
Looks like an XKB input handling regression.

Jj-stechmann 2025-09-25 github

Also happens on Fedora 42, with the standard German layout - being unable to type Umlauts, etc.

System Info, if it matters:
OS: Fedora Linux 42 (KDE Plasma Desktop Edition) x86_64
Kernel: Linux 6.16.7-200.fc42.x86_64
Packages: 3177 (rpm), 24 (flatpak)
DE: KDE Plasma 6.4.5
WM: KWin (Wayland)
CPU: AMD Ryzen 7 9800X3D (16) @ 5.27 GHz
GPU 1: NVIDIA GeForce RTX 3070 Ti [Discrete]
GPU 2: AMD Radeon Graphics [Integrated]
Memory: 30.45 GiB
Disk: 929.93 GiB
Locale: en_US.UTF-8

Steam Beta Branch: Stable Client
Steam Version: 1757650573
Steam Client Build Date: Fri, Sep 12 05:55 UTC -08:00
Steam Web Build Date: Fri, Sep 12 01:47 UTC -08:00
Steam API Version: SteamClient022

Cchenx-dust 2025-12-19 github

@Wolfen113 @j-stechmann Hey there!

Could you please have a try to downgrade libxkbcommon to 1.11.0? I found it breaks Steam Input after upgrade.
Hope it work.

WWolfen113 2025-12-19 github

@Wolfen113 @j-stechmann Hey there!

Could you please have a try to downgrade libxkbcommon to 1.11.0? I found it breaks Steam Input after upgrade. Hope it work.

I tried rolling back the library to 1.11.0. Unfortunately, I couldn't check if Steam worked because my entire Cinnamon environment broke on the old library.

Cchenx-dust 2025-12-19 github

Oh, you may also downgrade libxkbcommon-x11 as well. Sorry for my oversight.

If it doesn't work, you may try to use LD_PRELOAD to let Steam use the older library separately.

Jj-stechmann 2025-12-19 github

The most up-to-date release of libxkbcommon at the time of my comment was 1.10.0, so I don't know if that's the issue.

I'm now on arch with libxkbcommon 1.13.1-1 and the issue appears to be fixed - but obviously there are lots and lots of differences between when I reported this on fedora 42 and my current arch setup.

Ttriangelprisma 2026-04-11 github

still an issue, on fedora too ;/

DDisThoughts 2026-08-14 github

I can reproduce a very similar issue with the Faroese keyboard layout on Fedora KDE Wayland.

System:

Fedora 45 Rawhide
KDE Plasma 6.7.x / Wayland
Steam Flatpak (com.valvesoftware.Steam)
libxkbcommon 1.13.1
Faroese XKB layout (fo)

Behavior in Steam Overlay:

ASCII letters/numbers work
Control/navigation keys work: Backspace, Delete, Enter, Tab, arrows
Ctrl shortcuts work: Ctrl+A/C/X/V/Z
Pasting non-ASCII text works
Faroese-specific characters cannot be typed directly

Affected Faroese characters include:

á ð í ó ú ý æ ø
Á Ð Í Ó Ú Ý Æ Ø

For the acute vowels, the dead-key composition is lost and only the base letter appears. For direct non-ASCII keys such as ð, æ, and ø, no character is produced.

A few things I tested while narrowing this down:

The Faroese layout works correctly outside Steam Overlay in Konsole, KWrite, browsers etc.
The issue occurs in multiple Overlay text fields: chat, Notes, browser/search fields.
It reproduces with both Flatpak Steam and the RPM Fusion native Steam package.
Switching a game between fullscreen and windowed does not change it.
Forcing XWayland's visible layout from us to fo with setxkbmap -layout fo does not fix it.
Running Steam with XMODIFIERS=@im=none or with GTK_IM_MODULE=xim QT_IM_MODULE=xim XMODIFIERS=@im=none does not restore Faroese characters.
Steam Beta currently behaves the same.

I also found a separate local issue during testing: I had stale environment variables forcing IBus (GTK_IM_MODULE=ibus, QT_IM_MODULE=ibus, XMODIFIERS=@im=ibus) even though no IBus daemon was running. That caused printable keyboard input to fail completely in the Overlay for some games. Removing that stale configuration fixed ordinary ASCII typing, but the Faroese/non-ASCII issue described above remains unchanged.

Current session has no GTK_IM_MODULE, QT_IM_MODULE, or XMODIFIERS override set, and Faroese input works normally everywhere except Steam Overlay.

So this appears consistent with the issue described here: Steam Overlay is receiving ordinary key events correctly, but non-ASCII/XKB text input is not being converted/committed correctly.

Launch options