Gamepad not recognized if disconnect/reconnect or hot plugged

[corvusd]

Your system information

• Steam client version (build number or date): steam-runtime_0.20221019.0

• Distribution (e.g. Ubuntu): Ubuntu 20.04.5 LTS (64 bits)

• Opted into Steam client beta?: [Yes/No] Yes

• Have you checked for system updates?: [Yes/No] Yes

Please describe your issue in as much detail as possible:

Three weeks ago, playing Retroarch with Steam play together, Steam input recognized my friend's controller. Today it has not been possible to play with him because of this.
Investigating. If I disconnect and connect my controller locally. Retroarch or any game doesn't recognize it again. Before it worked right. I estimate this change about 3 weeks ago.
I have tried several gamepad: original Xbox 360 wired and arcade type. And Steam Gamepad. With same result.

Steps for reproducing this issue:

1. Launch a game with the controller attached.
2. Disconnect the controller.
3. Plug it in again.
4. The gamepad is not recognized.

[Argetlami]

Your system information

• Steam client version (build number or date): 1674790765
• Distribution (e.g. Ubuntu): Nobara (Fedora) 37
• Opted into Steam client beta?: No
• Have you checked for system updates?: Yes

Same issue, multiple controllers are working even at the same time if those are already connected when starting a game. While mid-game, connecting a new controller - or reconnecting an existing controller - makes that controller unresponsive in game. If the game was launched in Big Picture mode, these seemingly unresponsive controllers can still open the Steam Big Picture overlay with their guide button. These new and/or reconnected controller(s) are working - and properly showing up - in Steam Big Picture in-game overlay, yet not in game.

Happens with titles other than Retroarch too, at least with Snowrunner (1465360) and Sackboy™: A Big Adventure (1599660). Reproduced on Proton 7.0-5, Next, and Experimental, haven't tried the others. Controller hotplug has been previously working as expected with these.

Happens regardless whether Steam Input per-game configuration is set to forced on or forced off. Tested with an Xbox Elite Series 2 (xpadneo) controller, PS5 controller, and PS4 controller.

Edit: As a clarification, no Remote Play was used from my part. All my findings are on a single machine with multiple controllers attached.

[corvusd]

Yes, you are right. It is happen in whatever game and scenario.

[corvusd]

The issue still here. Very sad and annoying issue. Please valve team, try to fix this incredible issue. We can't plug-in our gamepad with a launched game. Or even if we suspend and awake the system. The client not see the gamepads. This not happens a moths ago.

[guide-bot]

I also have this problem where a controller cannot be added after a Proton game has started on my Linux computer. I also noticed that when I try to stream a game from my Linux computer to play on my Steam Deck, the Steam Deck controls do not work in-game. I think that both of these issues are symptoms of the same bug.

[corvusd]

Yes, I have very similar problems... I think is the same issue.

[ivyl]

This should be now solved with a Steam Runtime update. It should be picked up automatically, but if it takes time restarting Steam can speed things up.

[smcv]

More specifically, this is hopefully fixed by today's "Steam Linux Runtime - soldier" update (for Proton games, and most native Linux games on Steam Deck), or by today's "Steam Linux Runtime - sniper" update (for Retroarch specifically).