Can't create new collections or rename an existing one in desktop mode due to input box losing focus when launching virtual keyboard and won't take input from it
steamopenSteam clientDistro Family: SteamOS
ValveSoftware/steam-for-linux#11355 ·
opened 2024-10-16
by UsernamesAreNotMyThing ·
updated 2024-11-30 ·
1 comments ·
github
Steam client version (build number or date): Latest stable
Distribution (e.g. Ubuntu): Steam Deck
Opted into Steam client beta?: No
Have you checked for system updates?: Yes
Steam Logs: [generate by running this command in a terminal tar -zcvf ~/Desktop/steam-logs.tar.gz ~/.steam/steam/logs]
GPU: AMD
Please describe your issue in as much detail as possible:
In the dialog to create a new collection in your library, the text box loses focus immediately on launching the virtual keyboard, making it impossible to type without using an external keyboard or another computer. Even when clicking the text field with the keyboard already on screen, it still won't take input from it. The same issue also occurs with trying to rename an existing collection.
Steps for reproducing this issue:
Navigate to Library > Collections
Select "Create a new Collection"
In the dialog that appears, select the text input box.
Summon the keyboard with the X button. The input field is unfocused and won't receive any input.
I've had this issue for months. My workaround was to bind L3 to "Ctrl+V" (with V as a "sub" command, not "extra" IIRC), then type collection names into Kate and copy-paste them into steam with L3.
Your system information
Steam Logs: [generate by running this command in a terminaltar -zcvf ~/Desktop/steam-logs.tar.gz ~/.steam/steam/logs]Please describe your issue in as much detail as possible:
In the dialog to create a new collection in your library, the text box loses focus immediately on launching the virtual keyboard, making it impossible to type without using an external keyboard or another computer. Even when clicking the text field with the keyboard already on screen, it still won't take input from it. The same issue also occurs with trying to rename an existing collection.
Steps for reproducing this issue: