protonscr

Remote play has recently stopped working

steamclosed StreamingDistro Family: Fedora
ValveSoftware/steam-for-linux#11524 · opened 2024-11-27 by pjoc · updated 2024-12-04 · 4 comments · github
Ppjoc 2024-11-27 github

Your system information

  • Steam client version (build number or date): Steam Beta Branch: Stable Client
    Steam Version: 1731433018
    Steam Client Build Date: Tue, Nov 12 5:10 PM UTC -08:00
    Steam Web Build Date: Tue, Nov 12 2:03 AM UTC -08:00
    Steam API Version: SteamClient021
  • Distribution (e.g. Ubuntu): Fedora 41
  • Opted into Steam client beta?: [Yes/No] No
  • Have you checked for system updates?: [Yes/No] Yes
  • Steam Logs: [generate by running this command in a terminal tar -zcvf ~/Desktop/steam-logs.tar.gz ~/.steam/steam/logs]
  • GPU: AMD RX580

Please describe your issue in as much detail as possible:

Describe what you expected should happen and what did happen. Please link any large code pastes as a Github Gist

Steps for reproducing this issue:

  1. Run Steam on Fedora with Playstation input enabled. Installation is steam-1.0.0.82-1.fc41.i686 from RPMfusion.
  2. Run Steam Link on Google Chromecast, verify that PC, controller (PS5 Dual Shock) and connection are all working
  3. Click on Play (using Chromecast remote)
  4. See Steam Big Picture interface on TV
  5. Controller buttons do nothing. Touchpad moves the onscreen cursor. Clicking on touchpad changes to black screen with only the mouse cursor visible.
  6. Only way to escape is with Back button on Chromecast remote.
  7. This issue is recent (a week or so). Previously I was able to use a PS4 controller, an Xbox controller and a Stadia controller, all without problems.

steam-logs.tar.gz

Ppjoc 2024-11-28 github

Issue fixed by downgrading to steam-1.0.0.81-1.fc41.i686:
Steam Beta Branch: Stable Client
Steam Version: 1731433018
Steam Client Build Date: Tue, Nov 12 5:10 PM UTC -08:00
Steam Web Build Date: Tue, Nov 12 2:03 AM UTC -08:00
Steam API Version: SteamClient021

Both packages are based on the same version of Steam, so this may be a packaging problem.
Reported to RPMfusion at:
https://bugzilla.rpmfusion.org/show_bug.cgi?id=7117

Ppjoc 2024-11-29 github

In fact it's not a packaging issue, as I've had the same problem even after downgrading. This is my setup:

Fedora 41 with the Steam rpm up to date as noted above.
Chromecast dongle over fast WiFi (tested at 50Mbps and above) running the Steam Link app.
Various controllers including PS4, PS5, Xbox and Stadia.

On initial pairing of a controller, everything works. After leaving a gaming session and coming back, nothing works. Specifically, the Steam Link panel shows ticks for controller, network and PC, but the controller is non-responsive. If I disconnect the controller and repeat the pairing, it starts to work again. (I think the same has sometimes happened if I kill and restart Steam on the PC, but that doesn't always work.) I'm guessing that Steam Link on the Chromecast and Steam on the PC are somehow out of sync with each other. However force-stopping Steam Link and restarting it doesn't fix the issue, so maybe it's actually a problem with Chromecast.

Ppjoc 2024-12-04 github

After doing some tests with an Amazon Fire Stick (same setup), I've concluded that this is a problem with the Chromecast dongle. Will contact Google support. Apologies for the noise.

Kkisak-valve maintainer 2024-12-04 github

Hello @pjoc, since you determined that the issue is on the Steam Link standalone client side, that would make https://steamcommunity.com/app/353380/discussions/4/ a better place to continue discussing your issue because issues with the standalone Steam Link app are not tracked here.

Nothing extracted yet.