Your system information
- Steam client version (build number or date): 1747176658
- Distribution (e.g. Ubuntu): SteamOS
- Opted into Steam client beta?: Yes
- Have you checked for system updates?: Yes
- Steam Logs: go-s-controller-missing-controller-logs.tar.gz
- GPU: AMD Z2 Go (Rembrandt APU)
Please describe your issue in as much detail as possible:
Occasionally on booting up the device, the Steam client will recognize the Go S controller but it will not accept any input from the device. Inspecting the HID events from the controller, it works perfectly. The issue seems to lie somewhere in the Steam client. Restarting the Steam client works around the issue when it happens.
I've noticed that the bug most often happens on your first boot after an OS update, but it can affect subsequent reboots without updates as well. I've not had the bug occur yet if Inputplumber is disabled, but this seems like a bit of a red herring since the input tester in Inputplumber works perfectly while the Steam client is unresponsive to the controls.
Steps for reproducing this issue:
- From a fully updated SteamOS, apply a previous update (
sudo steamos-atomupd-client --update-from-url https://steamdeck-images.steamos.cloud/steamdeck/20250510.1000/steamdeck-20250510.1000-3.8.0.raucb works)
- Reboot the device
- After gamescope-session launches, try moving the controller.
If you got lucky, the controller will be unresponsive here.
Unfortunately, the failure rate here is more like 2% of the time so buckle up for an adventure 🐸
- Apply the most recent SteamOS update once again
- Reboot the device
- After gamescope-session launches, try moving the controller.
If the controller still works, time to go back to step 1 and start the whole process over again 🤠
I'd aim for at least 50 cycles, preferably more, without reproducing the bug to determine whether or not it's fixed.
Your system information
Please describe your issue in as much detail as possible:
Occasionally on booting up the device, the Steam client will recognize the Go S controller but it will not accept any input from the device. Inspecting the HID events from the controller, it works perfectly. The issue seems to lie somewhere in the Steam client. Restarting the Steam client works around the issue when it happens.
I've noticed that the bug most often happens on your first boot after an OS update, but it can affect subsequent reboots without updates as well. I've not had the bug occur yet if Inputplumber is disabled, but this seems like a bit of a red herring since the input tester in Inputplumber works perfectly while the Steam client is unresponsive to the controls.
Steps for reproducing this issue:
sudo steamos-atomupd-client --update-from-url https://steamdeck-images.steamos.cloud/steamdeck/20250510.1000/steamdeck-20250510.1000-3.8.0.raucbworks)I'd aim for at least 50 cycles, preferably more, without reproducing the bug to determine whether or not it's fixed.