Closed GrimmLinux closed 1 year ago
I have the same problem. The title is a bit misleading because this isn't an issue with the keyboard but the outcome is the same:
In the steam overlay I have to type every letter twice for it to show up. Exceptions are event keys like backspace or enter - those are functioning normally. The behavior is similar to how Dead keys work: The first key press does nothing but the second on does.
This is everywhere in the steam overlay:
I rarely type in the overlay so my first notice of this was on the 02.10.2022 (or the next weekend 09.10.2022).
My setup is different however: I'm not using FlatPak. This is with the normal Steam Client Beta installed from the Arch Linux repositories. The Soundcard and the SSD-Count in the steam report are wrong but I don't think they matter.
Same here. Steam Runtime installed from ArchLinux repositories too. system_information.log
@kisak-valve This has been happening for a while on the native Fedora package as well, not just on Flatpak Steam. Nobara suffers from this as well.
There's a new significant clue that I have just found: It seems that this issue only occurs with Windows games under Proton, the overlay works fine with Linux native games, I have tried with some games like Portal 2, Team Fortress, SOMA, etc., and I could type without issues.
This could be a difference with the Steam overlay interacting with Vulkan-based games versus OpenGL games.
@DomiStyle, @GrimmLinux, can you list some games you know are affected? More specifically, are there any OpenGL games which are affected or Vulkan games that are not affected?
@Mastergatto, can you check a native Linux game which uses Vulkan?
@kisak-valve
Not sure if there's a way to force OpenGL/Vulkan translation on certain games (please advise if needed), but using Steam Linux Runtime vs Proton irregardless - both did pre caching of Vulkan shaders, however with different results
Team Fortress 2 - Steam Linux Runtime - Processed Vulkan Shaders - No issue in overlay Team Fortress 2 - Proton Experimental - Processed Vulkan Shaders - Issue in overlay
Cyberpunk 2077 - Proton Experimental - Issue in overlay No Man's Sky - Proton Experimental - Issue in overlay
Counter Strike Global Offensive - Steam Linux Runtime - Processed Vulkan Shaders - No issue in overlay
@kisak-valve I tested a few games in my library:
OpenGL (Native):
OpenGL (Proton):
Vulkan (Native):
Vulkan (Proton):
ToGL (Native):
DXVK:
So yes, this seems like a Proton issue.
@Mastergatto, can you check a native Linux game which uses Vulkan?
I have tested Valheim which is Vulkan based game and it is native on Linux, and I can type just fine on overlay. I have tried also its OpenGL backend, same here, no issue whatsoever.
Thanks, since running games with Proton is a common factor here, I've gone ahead and transferred this issue report to the Proton issue tracker. One more quick detail that might be interesting to a Proton dev is if running a game with some older point releases of Proton have the same quirk behavior.
@kisak-valve
Testing on No Man's Sky
Proton 6.3-8 - Issue Proton 5.13-6 - No issue
Proton 7 was not doing this up until recently so I didn't expect 6.3-8 to have the same behavior
Hello,
I am now encountering this issue too after switching from debian (stable/bullseye/11) to fedora (37). What's interesting is that, being lazy, I did not format my home partition nor the partition my steam library is on. Meaning I did not change my steam configuration, proton version, game installation/version or recreate the proton prefix (steam itself had to be reinstalled though).
In short (the same day, using the same files):
Debian 11 + Deep Rock Galactic + proton 7 = ok Fedora 37 + Deep Rock Galactic + proton 7 = bug
Recently began encountering this issue in Ultramarine 36. Tried several older proton versions with several different games, no change.
I am encountering this issue on openSUSE TW, KDE Wayland. Unrelated but might help, pasting into steam chat (outside of overlay, in normal mode) sometimes doesn't work.
Having the same issue as of Mar 23 2023 on Debian 11
Also having the same issue in April 2023 on Fedora Workstation 37 (GNOME)
Still happening on the latest beta with the new overlay design, this really makes the new notes feature unusable.
OS: Arch Linux Runtime version: disabled Proton version: experimental (I'd attach the full system specs but I can't find a way to copy them from the new UI)
I came here to report the same thing as @Soulsuke. I was hoping the new beta overlay would fix the issue but it does not. At the very least this indicates the issue probably isn't related to anything that was overhauled.
Another component to this issue, in some other games (Cassete Beasts is one example), in addition to the text input issue, after leaving the steam overlay, the controls appear to get stuck where they rapidly highlight menus sequentially. It seems similar to when you start a controller and one of the joystics is held in a forward or backwards position and your in-game character perpetually moves in that direction until you reset the controller.
When this happens, it's almost impossible to select any menu with either the mouse or the keyboard as the game is perpetually generating input and scrolling through menus.
I'm not using a controller at all, just a mouse/keyboard.
Perhaps the overlay is detecting phantom inputs which make it necessary for a user to repeatedly hit keys to get letters to appear.
any news on this? it's getting really annoying to either tab out or hhaavvee ttoo ttyyppee lliikkee tthhiiss
I don't understand...they made this great new client, hardware accelerated on Linux and all...yet this bug persists lol
It's now been 8 months and this was supposedly passed on to Proton development but has not been touched. Still an issue from regular to flatpak and even in the new updated UI. Looks entirely different, has the identical issue. Wild.
Not sure if it's already been reported, but: the issue goes away for me by disabling ibus.
However this is only viable on DEs not relying solely on ibus for input, so while it works on i3 it may cause other kind of issues for others (eg. a friend reported that disabling ibus prevents any kind of input on Steam Overlay and on certain other applications like Telegram).
Hello @Soulsuke, I'm doubtful that this will work, but if you completely close Steam, enable ibus to be consistent with reproducing the issue, then run IBUS_ENABLE_SYNC_MODE=1 steam
from a terminal, does that workaround the issue?
@kisak-valve Just tried it out, the issue is still present even if i set IBUS_ENABLE_SYNC_MODE=1
. To be extra certain I tried to disable ibus again, and the issue isn't present that way
I use fcitx5 with these environment variables. As far as I know ibus is not running.
IMSETTINGS_MODULE=fcitx
GTK_IM_MODULE=fcitx
QT_IM_MODULE=fcitx
XMODIFIERS=@im=fcitx
SDL_IM_MODULE=fcitx
Tried IBUS_ENABLE_SYNC_MODE=1
anyway and the issue was still present.
I use fcitx5 with these environment variables. As far as I know ibus is not running.
If you are using gnome as DE it might be started any way. Check your processes with:
$ ps aux | grep [i]bus
In case it is running you can try forcefully disabling it by renaming the executable (and then reboot):
$ sudo mv /usr/bin/ibus-daemon{,.dist}
Oh sorry, I'm using KDE. That grep returned no result.
+1
OS: Nobara Linux 37 (Thirty Seven) x86_64
Host: OMEN by HP Laptop 15-ce0xx
Kernel: 6.4.10-202.fsync.fc37.x86_64
Packages: 2737 (rpm), 9 (brew), 37 (flatpak)
DE: GNOME 43.2
CPU: Intel i7-7700HQ (8) @ 3.800GHz
GPU: NVIDIA GeForce GTX 1060 Mobile 6GB
GPU Driver: nvidia-driver 535.98-1
Mesa: 23.2.0
Memory: 4409MiB / 15926MiB
GE-Proton8-13
Proton Experimental (2023-08-22)
8.0-3
7.0-6
Steam Version: 1692390949
Steam Client Build Date: Fri, Aug 18 21:39 UTC -08:00
Steam Web Build Date: Fri, Aug 18 22:21 UTC -08:00
Steam API Version: SteamClient020
GE-Proton8-13 Enable smooth scrolling in web views (requires restart) Enable GPU accelerated rendering in web views (requires restart) Enable hardware video decoding, if supported (requires restart)
SS | GA | HVD | Broken |
---|---|---|---|
1 | 1 | 1 | 1 |
1 | 1 | 0 | 1 |
1 | 0 | 1 | 1 |
1 | 0 | 0 | 1 |
0 | 1 | 1 | 1 |
0 | 1 | 0 | 1 |
0 | 0 | 1 | 1 |
0 | 0 | 0 | 1 |
Due to Armored Core 6 using EAC and the associated launch pop-up killing the overlay normally, I gave gamescope a go. To my surprise, I'm able to type normally in the overlay this way.
As of the below versions, this seems to have been resolved.
Steam Version: 1695334486 Kernel: 6.5.3-200.fsync.fc38.x86_64 Proton: 8.0-3
I'll wait a bit to see if there's any further updates on here.
Hello @GrimmLinux, see https://github.com/ValveSoftware/steam-for-linux/issues/9325#issuecomment-1731669609.
@kisak-valve great - thank you so much! Can confirm this is working then.
Your system information
Please describe your issue in as much detail as possible:
Details:
After a Steam Flatpak update a few weeks ago (update from the Steam client when launching Steam), a new bug surfaced for me with the in-game Steam overlays. Whenever I'm in the Steam overlay, the overlay does not register every other key I press, requiring you to double up keys.
So if I wanted to type "Hello" in the overlay (the shift key would count as 1 key), I would have to type "Heelllloooo".
Specs:
Steam: flatpak 1.0.0.75 OS: Freedesktop.org SDK 22.08 (Flatpak runtime) (Zorin OS) KERNEL: 5.15.0-48-generic CPU: 12th Gen Intel Core i5-12400F GPU: NVIDIA GeForce RTX 3080 Ti GPU DRIVER: NVIDIA 515.65.01 RAM: 16 GB
OS: Nobara Linux 36 (Thirty Six) KERNEL: 5.19.14-201.fsync.fc36.x86_64 CPU: 12th Gen Intel Core i5-12400F GPU: NVIDIA GeForce RTX 3080 Ti GPU DRIVER: NVIDIA 515.76 RAM: 16 GB
Steps for reproducing this issue: