I have the same issue. Issue only exists in Big Picture Mode. It was introduced into the stable release a couple of months ago for me. Exact same behavior you described. Same results on Linux Mint 21.3 and Linux Mint 22. Both systems ran Xfce. Issue still not resolved, 6-21-25. Now in 2026, Jan 8th. This issue has been plaguing me for almost 2 years. Considering Valve is trying to push SteamOS further and promote a console like experience, using BPM at the forefront, I don't understand why this issue is not being given any attention. I guess if I was on a Steam Deck or the upcoming Steam Machine, this would work. I guess I'll just sit around for another year or two or three until this is maybe resolved or just not be able to use the software the way it's intended to work.
I have the same issue. Seems like no matter the keyboard layout I choose for Steam keyboard overlay, along with the selected keyboard layout, pressing certain letters like: O, R, T, L will act as pressing physical arrows keys, just like Dvorak keyboard layout functions. I tried editing the localconfig.vdf and change the SteamOverlay keyboard setting but to no avail.
O is the Up Arrow
R is the Right Arrow
T is the Down Arrow
L is the Left Arrow
I'm not sure that is correct.
R, T and O are consistently broken for me, but I have no problem with the L key.
Another thing, the keyboard worked correctly when I tried in a Gamepad UI session using this:
https://github.com/ChimeraOS/gamescope-session-steam
Valve, I hope you're tracking this, since it seems to affect more Linux users.
Can you reply and let us know if this on your radar?
Manjaro XFCE
I have the same problem.
O is the Up Arrow
R is the Right Arrow
T is the Down Arrow
Same problem for a few months now.
q goes left, but only if it's the 1st letter typed, i.e.:
Happens on both stable and beta client.
This is also occurring for me in CachyOS. Submitted a ticket that I didn't realize was a dupe.
I'm curious if there's some bigger rework for Steam BPM on Linux coming, in the future. There's a lot of issues with it.
How come this doesn't happen on Deck?
same thing exists on arch (x11)
only exists in big picture mode's overlay for me
Bumping this.
Your system information
Steam client version (build number or date): 1735842154 (Thu, Jan 2 19:10 UTC -08:00)
Distribution (e.g. Ubuntu): Ubuntu
Opted into Steam client beta?: Yes
Have you checked for system updates?: Yes
Steam Logs: (will add later if needed)
GPU: NVIDIA
Happening on Nixos > Hyperland using stable or beta for many months now. same as previously reported with o,t,r keys.
Having the same issues on Mint Cinnamon, trying to get the on-screen keyboard working with my game.
Happening on Nixos > Hyperland using stable or beta for many months now. same as previously reported with o,t,r keys.
I switched to Bazzite, and the OSK DOES work on that distro. I believe I saw something about a special Steam keyboard driver or a Kwin window script for the OSK. I am not at my home, so I cannot verify that right now. I hope that it leads you in the right direction.
Having the same issues on Mint Cinnamon, trying to get the on-screen keyboard working with my game.
As a game dev? I don't think you can do anything about it. It's a Steam client issue. It doesn't happen on SteamOS, though, so no issue on Steam Deck, which AFAIU is where you'd need the OSK to work in your game. If you're trying to test OSK on Cinnamon, it won't work as expected until the issue is fixed on Valve's side. (Unless Cinnamon does whatever Bazzite did - maybe it works on Bazzite thanks to HHD.)
Same issue for me, using Endeavour OS which is arch based same as steamos on steamdeck
it only occurs in overlay mode
Same issue for me on Pop!_OS.
+1 Same issue with R,T, and O keys on Bazzite.
Also seeing the issue running Steam in Docker with Games on Whales (Wolf).
EndeavourOS, same issue. Occurs only in big picture mode.
Another EndeavourOS user here, same issue.
Happens when using physical keyboard or the steam virtual keyboard.
Looks like this problem is exactly the same as https://github.com/ValveSoftware/steam-for-linux/issues/11236, according to the comment saying:
O is the Up Arrow
R is the Right Arrow
T is the Down Arrow
which is the exact same behavior i seem to have in that issue
Having this issue on Plasma running Arch with every kernel I have installed. Only happens in games, the guide button chord OSK doesn't have this issue and the O, R, and T keys work properly outside games launched with Big Picture. Relaunching doesn't fix it.
Certain keys also seem to activate my 6th Launch key for whatever reason, which I have bound to open ROG Control Center. Weird.
Can confirm the issue on gnome wayland (nobaraOS)
It seems the issue happens on Linux for Wayland environments. Which could explain why it's not happening on Steam Deck I think they have xwayland or maybe even x11 not 100% sure.
Was someone able to reproduce this on a non wayland environment?
The steam deck uses a wayland compositor, and im able to reproduce on a non-wayland environment which i also reported on https://github.com/ValveSoftware/steam-for-linux/issues/11236 with a lot more detail
Same here on Cachy + KDE (doesn't seem to make a difference though).
Tested a few different Steam osk layouts as well in case it made a difference but no luck there.
I'm on OpenSUSE Tumbleweed using KDE Plasma and I've also had this issue when using Big Picture mode and trying to use the on screen keyboard with my controller.. I don't know if this was the game itself or part of this issue but when I shifted for an uppercase letter, it only entered a lowercase one. Otherwise R, O, T are an issue still.
Having the same issue with QRTO being arrow keys on Manjaro KDE.
Same issue on Fedora 43 KDE
I have the issue on Bazzite, when trying to use letters like O, T, etc it will act as a directional input instead of typing the character.
I am experiencing the same issue with the Q, R, T, and O keys. This problem has been ongoing for a long time and does not appear to be under review or receiving any attention.
Same issue:
Linux Mint 22.1 Cinnamon
Same issue in CachyOs (arch)
Same with EndeavourOS (arch) and Steam Version 1766451605, Client 023
The issue seems to be solved now.
While it was fixed i was running with XMODIFIERS=@im=xim so minecraft doesnt drop inputs
I dropped that environment env var, so it could be that both dropping the env var and steam updating fixed the issue
All keys work as intended now
The issue seems to be solved now.
While it was fixed i was running withXMODIFIERS=@im=ximso minecraft doesnt drop inputs
I dropped that environment env var, so it could be that both dropping the env var and steam updating fixed the issue
All keys work as intended now
The issue is not resolved.
As of Steam stable 1766451605, if you launch a game and go into any text field with or without a controller, those specific keys (r, t & o) cannot be typed. If Big Picture is not running, this issue still appears if you bring up the Steam On Screen Keyboard and try to type those keys.
In addition, if in the Big Picture main menu, while a game is running, q focuses to the left sidebar menu.
Your fix doesn't address anything regarding this problem.
I can type all letters, meybe our problems were the same but different causes for it, im using steam version 1767909714 beta channel
Mine is higher than yours so try beta?
Just tested with the Jan 8 beta, and nope. This is still an issue specifically when the virtual keyboard is used in the overlay.
This is not however an issue with BPM keyboard in general, it seems to be specifically an overlay issue.
For example, just running BPM and using the search bar at the top to invoke the virtual keyboard, everything seems to work as expected.
But running any game and using the BPM overlay, for example try to rename something in the controller layout editor to invoke the keyboard and the issue is present.
Same issue with the overlay keyboard both in Big Picture and in SteamVR.
Edit: also happens when using the android keyboard through Steam Link
EndeavourOS with KDE Plasma
Same issue happening on me now.
Lubuntu 24.04.3
Gtx 1660s
Ryzen 7 3700x
Same issue in Arch with i3 on X11.
Same issue on here. I can reproduce this reliably on my system and it appears configuration-independent. Everything I have tried did not work. And I tried everything.
Environment:
Linux Mint 22.3 (Ubuntu 24.04 base), Cinnamon (X11)
Kernel 6.17.x
NVIDIA proprietary driver
Controller: Manba / Zhixu Xbox-compatible clone
Steam: Gamepad UI / Big Picture
Repro details / scope:
Occurs only while a game is running (in-game overlay / text entry context).
The on-screen keyboard works normally in the main Big Picture menus, but inside games some keys (notably Q, R, T, O and sometimes numbers) are interpreted as UI navigation rather than inserting characters.
This affects both the Steam on-screen keyboard and a physical keyboard (letters trigger navigation / focus changes rather than typing).
Config / workaround attempts (did not resolve):
Reset Desktop Layout and Guide Button Chord layout to templates/defaults
Removed “Show Keyboard” bindings where applicable
Toggled Steam Input options (enable/disable), guide/chord related options
Toggled overlay-related settings (enable/disable)
Cleared Steam input/config files (controller_configs, steaminput.vdf, config.vdf/localconfig.vdf) and restarted
Secondary behavior observed during troubleshooting:
After disabling various controller/overlay options, a new symptom appeared: typing worked briefly (~0.5s) and then a Big Picture UI “back/whoosh” sound played and the text field lost focus, preventing further typing. Restoring Steam controller-related settings returned behavior to the baseline issue above.
Impact:
Controller / Input
Steam Settings
Launch flags / environment
STEAM_DISABLE_TEXT_INPUT=1STEAM_USE_OLD_BIGPICTURE=1-oldbigpicture-vguiConfiguration reset
controller_configssteaminput.vdfconfig.vdflocalconfig.vdfTemporary change in behavior occurred after altering settings, but restoring defaults returned to the baseline issue.
The behavior resembles a UI navigation layer activating during text entry, causing keyboard input to be interpreted as controller navigation. The issue occurs with both the virtual keyboard and a physical keyboard.
100% reproducible on this system.
Also ran into this problem while trying to name a planet in No Mans Sky, was unable to type the letters r/t on the physical keyboard and the virtual keyboard wouldn't work for them either, was trying to select with pad/mouse too but the selection just jumps away from the desired key no matter what.
Running on (K)ubuntu 24.04 and XBox Controller via USB, Steam installed from deb package.
Happens on starfield as well. Ubuntu 25.10 - No controllers connected but using BPM with physical keyboard. Steam installed from deb package.
Happens in Debian 13 Trixie, Flatpak and .deb versions..
Game: Enshrouded..
I think it's a Big Picture Mode bug in steam.. Because if I disconnect the controller and use physical keyboard i don't get any bugs.. besides, outside the game, the virtual keyboard works fine, but when I try to touch those keys ingame they function as physical arrow keys.
I've been having this issue with Big Picture Mode for the past year, EndeavourOS + KDE Plasma (Wayland) on my desktop (RTX 3050) and my laptop (Intel 12th gen integrated graphics)
even if I hit the "approve" button on the keyboard control popup that KDE Plasma gives, keyboard still gives the broken behavior described by others
This is still an issue. I'm using cashyos And some of the keys are indeed unselectable they just move up to other buttons
Just wanted to add this is happening to me too, I have the latest version of Bazzite with KDE Plasma desktop, same as everyone above the R, T keys act as arrow keys and the left/right arrow keys seem to act as up/down inputs
For some reason this is much more prevalent in-game as opposed to browsing the store for example, and impacts any plugged in keyboard as well as the virtual keyboard while steam big picture is running.
Outside big picture I have no issues
It happens in both the stable and latest beta branch
this is a game breaking issue thats been going on for a LONG time now
Same issue on cachyos, a workaround for me was to press shift and use a capital version of the letter.
Edit: - Updated to steam beta.
I opened steam settings, tried on random field, clicked on O a bunch of times, it didnt move as before..
first nothing happened, then suddenly O R and T worked.
Started a game, back to same error as before. So it's not fixed... got my hopes up, and then crushed.
Steam Version: 1778548034
Same issue on Bazzite Desktop version using Steam Big Picture mode.
Same issue on Xbox series X controller as an older xbox 360 controller, both connected through USB.
Tried multiple games, same issue on all of them.
Capital Letters on virtual keyboard, still didn't work.
Capital letters on external keyboard is a temporary workaround that at least enables the letters to be used.
OS: Bazzite Nvidia Open - Stable (F44.20260511)
Kernel: 6.19.14-ogc2.1.fc44.x86_64
Steam Version: 1778281814
Replying to https://github.com/ValveSoftware/steam-for-linux/issues/11158#issuecomment-4438406304
Perhaps like you, it was only fixed for a moment and thats when I noticed capitals were working.
It later started happening again, so likely capitals do not solve anything and clearly the issue is intermittent or dependent on some condition.
This issue is also happening to me. I'm using the latest versions of Steam, Arch Linux, and Hyprland.
Sadly this makes the on-screen keyboard unusable with the new Steam Controller too.
Happening to me as well, with or without my steam controller. This is embarrassingly bad, something like this should be priority 1 for fixing. Seeing as how it hasn't been resolved in literal years kills my faith a little.
Still happening to me.
Also not working for me on Fedora 44.
Just bought a Steam Controller. So now I gotta use big picture. Turns out it's not very usable because of this.
Disappointed to see this is a 2024 issue.
I have this issue also. I am on the waitlist for the Steam Controller and am disappointed that this might prevent me from being able to use it.
I have this issue also. I am on the waitlist for the Steam Controller and am disappointed that this might prevent me from being able to use it.
Simply alt tab out of big picture, write what you want into the start menu, and copy paste it back into big picture.
It is a pain but totally usable, only a few letters are problems.
I have this issue also. I am on the waitlist for the Steam Controller and am disappointed that this might prevent me from being able to use it.
Simply alt tab out of big picture, write what you want into the start menu, and copy paste it back into big picture.
It is a pain but totally usable, only a few letters are problems.
Except two big points:
Fix the problem.
Replying to https://github.com/ValveSoftware/steam-for-linux/issues/11158#issuecomment-4453488175
Theres an alt tab chord on your steam controller, just open notepad in the background.
Hold the 3 dot button and your touchpad becomes usable regardless of your current mapping.
I do not need a keyboard to do what i describe.
I would like them to fix it too, just trying to help people out in the meantime.
Edit: why the thumbs down? My mistake for offering workarounds to this game breaking bug.
Replying to https://github.com/ValveSoftware/steam-for-linux/issues/11158#issuecomment-4453504070
Why assume everyone has the Steam Controller? Without it, you'd need to know to set up the chord binding I mentioned.
Stop providing advice with premium, sold-out devices.
Replying to https://github.com/ValveSoftware/steam-for-linux/issues/11158#issuecomment-4454641392
The alt tab chord exists by default on all controllers, steam/guide button + start.
The mouse control override also works on all controllers but would use the stick instead of touch pad.
Your responses are borderline rude and not productive, please be more kind. I am only trying to help people. Just because you may not have a Steam Controller doesn't mean the advice wont be helpful to other people who come across this thread -- and again its not exclusive to a Steam Controller anyway.
Cheers and let's maintain a positive vibe, we're all on the same team here.
Hey, I decided to use the Big Screen keyboard again and Q, O, T, R, L keys are still not working as they should on my system as well.
(Arch on Gnome Wayland)
It's been a long time, I was hoping for this to catch some attention already.
CachyOS same thing here virtual steam keyboard and physical keyboard won't type some keys, R,T, and O.
Just adding here in hopes this gets some attention
SWITCHING TO DVORAK FIXED IT
WHYYYYY????????
Hoping this get a bit more attention from the devs, as I can't fully use my new Steam Controller in games that require some text input (Like PoE2 where the search bar is really useful). I can confirm that when in Big Picture Mode, even the physical keyboard can't type R T or O.
I'm using Arch with Hyprland, and since @blakeblair comment seems to point to a layout issue, I'm using the us intl XKB variant.
This should really get looked at before the release of the Steam Machine, since I guess it will be a big part of it to use the virtual keyboard with a controller.
Issue here as well running bazzite KDE, kinda bummer with the new steam controller and all.
+1 on this issue, Bazzite in Desktop mode, KDE Plasma version in the latest Bazzite:stable image. Can confirm the Q, R, T, and O keys do not function in the Big Picture Mode overlay in any game.
using ISO DE layout here. Yep. Still an issue, the Q, R, T, and O buttons won't work. And here I thought I was the only one with this VERY specific issue. Kinda a relief and a bit disappointing to see that it's that widespread. Hope we will get a fix really soon, since the new Steam Controller is fire. But man, I was unable to log into my games because my passwords were always wrong.
In the meantime, what I'm doing as a workaround is just typing my stuff out in Discord and then copy+pasting it into Steam.
It's faster than typing with a controller anyway, so this workaround makes it not that bad.
Valve please fix
I configured more guide button chords for ctrl c and ctrl v because I find the "paste button" doesn't work on the onscreen keyboard sometimes.
With that I can guide+start to alt tab, type into another program, select it, copy, alt tab back, paste, all with relative ease.
Still incredibly annoying and I wonder if there's anything we can do to raise awareness of this issue?
Linus from Linus Tech Tips has been adventuring into the land of Linux gaming lately and it might actually be possible for us to get this topic raised on this Fridays Wan show if we post this in the subreddit. Other Linux gaming related issues have been brought up there and were promptly fixed because of the awareness it raised.
Raising awareness to the issue and how game breaking it is might be all we need to get the ball rolling.
@Unreal-Dan This thread is already pretty active lately and it's a big enough issue. At this point, I'd say Valve is already aware of it.
The issue very well could be related to Wayland which might be the reason why it's taking longer. It would be nice if Valve communicated a bit better on issues like these so we could all know what the status of the issue is.
@Unreal-Dan This thread is already pretty active lately and it's a big enough issue. At this point, I'd say Valve is already aware of it.
The issue very well could be related to Wayland which might be the reason why it's taking longer. It would be nice if Valve communicated a bit better on issues like these so we could all know what the status of the issue is.
No somebody above said it occurs on arch with x11.
Also if Wayland was related id wager it would happen to more programs than just steam big picture.
Its steam, and they haven't communicated anything yet so why would you assume it is suddenly on their radar?
Its been years.
Arch on Wayland, virtual keyboard not working at all. I can open it automatically or manually, but cannot type anything. Tested on multiple games, physical keyboard works fine.
Arch on Wayland, virtual keyboard not working at all. I can open it automatically or manually, but cannot type anything. Tested on multiple games, physical keyboard works fine.
Not related to this issue
Similar to other reports. Bazzite (Linux 6.19.14-ogc5.1.fc44.x86_64), QRTO keys will not work while a game is running, on overlay, not exclusive to Big Picture mode. Affects both physical and Steam Onscreen Keyboard.
Similar to other reports. Bazzite (Linux 6.19.14-ogc5.1.fc44.x86_64), QRTO keys will not work while a game is running, on overlay, not exclusive to Big Picture mode. Affects both physical and Steam Onscreen Keyboard.
I've experienced this too. Issue does not occur in bazzite-deck image running gamemode-wayland session. Only in Plasma-desktop session.
Encountering this issue myself on Bazzite.
SWITCHING TO DVORAK FIXED IT
WHYYYYY????????
That did not work for me.
I've also noticed the arrow keys on the software keyboard aren't acting right; they change the currently selected key.
Same issue for me. Arch Linux and xlibre. Hopefully this can get fixed soon.
Same issue for me on Linux Mint 22.3 - Cinnamon 64-bit and steam version: 1781329812.
For me when i press the keys it switches to a different key without using the clicked one. While typing in steam instead of in a game (while a game is open in big picture mode) it just closes the keyboard and loses focus on the selected text box.
the "o" pushes my selected key to "0",
the "t" pushes my selected key to "g",
the "r" pushes my selected key to "t" which then when clicked pushes again to "g".
Having the same problem on Fedora 43 with KDE, it's a pity bc otherwise I really like using the steam controller
bazzite, happening to me aswell R T O only tho, on both physical and steam keyboard only in bpm
I do believe I've found a fix for this issue. Literally making an account just to share this.
I was having the same issue and isolated the failing layer.
Raw evtest capture from the Steam/Bazzite virtual input device shows the OSK
emits the correct Linux key events:
KEY_Q
KEY_R
KEY_T
KEY_O
I then launched Steam with -cef-enable-debugging, attached DevTools to the
game's SP Overlay target, and logged the DOM keyboard events. Steam exposes:
key: "q", code: "ArrowLeft", keyCode: 81
key: "r", code: "ArrowRight", keyCode: 82
key: "t", code: "ArrowDown", keyCode: 84
key: "o", code: "ArrowUp", keyCode: 79
So the kernel/uinput event is correct, but KeyboardEvent.code is malformed
inside the Steam CEF overlay. The overlay navigation appears to consume that
arrow code.
As a proof of cause, I overrode the KeyboardEvent.prototype.code getter in
the SP Overlay page only for these inconsistent pairs:
q + ArrowLeft → KeyQ
r + ArrowRight → KeyR
t + ArrowDown → KeyT
o + ArrowUp → KeyO
That immediately restored Q/R/T/O entry on both the OSK and physical keyboard.
The proper client fix should be in the Linux overlay/OSK event construction or
normalization before DOM dispatch.
Not gonna lie, I used chatgpt for pretty much all of this. Attached is the script I used to create a patched launcher, as well as the info I passed onto steam support in the hopes they'll make an official patch. Use this at your own risk; I can confirm it works on bazzite stable F44.20260629 with KDE as the frontend.
I just noticed this started happening recently after I got my steam controller and couldn't type certain letters. Wild that this has been going on for nearly two years now. T and O never work. Q will only work if it's not the first letter and R will only work if it's not the last letter.
I just switched to Dvorak, learned that, all good now. XD
Still a thing, much sadness... 😞
Steam, Fix this issue!
Why is this still a thing? How do I fix it?
@TheEnder515 has a solution above but it requires patching the Steam launcher so I haven't tried it.
@TheEnder515 has a solution above but it requires patching the Steam launcher so I haven't tried it.
@SimonBrazell It creates a seperate launcher altogether. It doesn't replace the old one. This new launcher launches steam in Big Picture mode. I've got another that launches in desktop; I just haven't published it yet.
This was fixed for me in the latest Steam Beta Client
Quickly tested the newest steam beta and it does seem to be fixed. Finally.
Yep can confirm it works now on the latest beta build.
Your system information
tar -zcvf ~/Desktop/steam-logs.tar.gz ~/.steam/steam/logs]Please describe your issue in as much detail as possible:
Describe what you expected should happen and what did happen. Please link any large code pastes as a Github Gist
When trying to enter any text inside Steam Overlay while running a game, input from some keys is ignored or triggers another action (like switching to another input field).
It doesn't matter if I use a physical keyboard, or a controller and the On Screen Keyboard.
This only happens for some keys, at least "r", "t" and "o".
This issue can be reproduced in both Desktop Mode and Big Picture.
I have tried on 2 boxes running Archlinux, one has an AMD gfx card, the other has an Nvidia card.
Expected behavior:
Steam Overlay lets me enter text using all keys using both the On Screen Keyboard and a Physical Keyboard.
Observed behavior:
Steam Overlay ignored some keys on both the On Screen Keyboard and a Physical Keyboard when entering text.
Steps for reproducing this issue:
Some keys don't do anything, or seem to trigger another actions, such as moving to another input element.
The "o" key consistently fails to do anything, "r" and "t" sometimes work after a fresh Steam launch, and then also fail.
a. I have tried using a Steam Controller, a Dual Sense controller and a physical keyboard.
This does work.