@kisak-valve I just upgraded to the latest non beta Steam - which is apparently a bit newer than the beta where this bug was 100% reproducable. So the Jan 31 build of Steam fixes this bug! woot!
I have the same problem on Ubuntu 24.04. Weird that this problem is reoccuring...
same problem, fedora 41 in big picture... "o" goes up, "t" goes down.
This is still unresolved. Please reopen.
I'm having the same issue as @twoda5h. Using Bazzite 41 with big picture: "q" goes left, "r" goes right, "o" goes up, "t" goes down. This happens on both a physical keyboard and the on-screen keyboard. I'm trying to chat in the game "Sky: Children of the Light". Cannot find any workarounds and changing to Steam Beta Update did not fix my issues.
Edit: Since my issue is slightly different from this one, and I doubt this one will be re-opened since the original reporter was able to resolve the issue, I've created a new one here with more details:
https://github.com/ValveSoftware/steam-for-linux/issues/11588
This is still an issue on non-beta Steam.
Confirm still an issue, Fedora 43 kinoite with steam as an overlay, stable
@petar-andrejic if you want updates on this, subscribe to #11158 <- I know the ticket numbers are similar, but it's tracked in that one.
4 months later and this is still an issue. I've been trying to trace it down but when playing Elden Ring nightreign it's effecting the OSK when trying to set a miltiplayer password and it's very annoying.
Your system information
Please describe your issue in as much detail as possible:
Expected: on-screen keyboard (provided by big picture mode?) should work for all keys.
Actual behavior: Some keys do not work - if either clicked on the key image with the mouse or with the physical keyboard. For instance the "r" key on my US keyboard doesn't enter an R (or any other character) into the text entry box. Instead the highlighted key on the graphical keyboard moves to the right to highlight the T key.
This is a regression from the stable Steam client which (though the graphical keyboard is less pretty) does work correctly.
Steps for reproducing this issue:
I'm happy to add further details if it would help track this down. For now I'm moving back to use the stable version of the client.
Update: In my original report I said I was on Ubuntu 22.04. I'm actually on 22.10.