Steam client version (build number or date): Jan 10 2020
Opted into Steam client beta?: Yes
Have you checked for system updates?: Yes
Please describe your issue in as much detail as possible:
Most desktop environments (i.e., KDE, GNOME, MATE, XFCE) have keyboard repeat enabled. Normally this wouldn't pose an issue, but with the Steam Controller, there is an issue with Tab repeat. When attempting to switch windows with the Steam Controller (SteamBtn+Start), holding the SteamBtn down will register as the tab key being held down. This results in a Alt-Tab menu which strobes at the repeat rate of your keyboard. This renders the functionality useless to the average person.
I located the keycode for Tab using xev. Using xset -r 23 worked for my keyboard to disable Keyboard repeat for the tab button specifically, so I set up autostart to launch **xset -r 23" on startup.
The solution was to change the exec line in Steam's .desktop file to bash -c "steam %U && xset -r 23"
Steps for reproducing this issue:
Open Steam
Use controller to Alt-Tab (i.e., SteamBtn+Start)
Continue to hold SteamBtn
I'm surprised I couldn't locate any documentation for this issue, but it may be due to the specificity of the problem. If you're a Valve employee reading this, thank you for taking notice!
Your system information
Please describe your issue in as much detail as possible:
Most desktop environments (i.e., KDE, GNOME, MATE, XFCE) have keyboard repeat enabled. Normally this wouldn't pose an issue, but with the Steam Controller, there is an issue with Tab repeat. When attempting to switch windows with the Steam Controller (SteamBtn+Start), holding the SteamBtn down will register as the tab key being held down. This results in a Alt-Tab menu which strobes at the repeat rate of your keyboard. This renders the functionality useless to the average person.
I located the keycode for Tab using xev. Using xset -r 23 worked for my keyboard to disable Keyboard repeat for the tab button specifically, so I set up autostart to launch **xset -r 23" on startup.
The solution was to change the exec line in Steam's .desktop file to
bash -c "steam %U && xset -r 23"Steps for reproducing this issue:
I'm surprised I couldn't locate any documentation for this issue, but it may be due to the specificity of the problem. If you're a Valve employee reading this, thank you for taking notice!