Change:
Describe the bug Steam Remote Play no longer works. The client never manages to start, and instead prompts a "The streaming client exited unexpectedly (2)" message. To Reproduce Steps to reproduce the behavior: Steam invited by a friend to play Steam Remote Play Together. invitation. Additional context I get the following line in the console logs shortly before the client crashes. It complains about a missing , but said library is present in the folder. I haven't managed to find information on that library by searching the web, other than many games and the Steam client itself seem to fail when it is not found. I also tried using , but it did not work. Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
launching steam with makes this work, but controller input does not seem to work on the remote client, unsure if that's related.
I have the same issue, as in client can connect to my session and keyboard/mouse works, but controller is only visible, but no input is being detected. with a steam controller it's even possible to navigate the steam overlay, but it's impossible to control any game. Is there an issue for this already, otherwise would probably make sense to create a separate issue? Here is the same thing happening on other distros: several users in this thread also seem to experience this. So to clarify a Windows 10 remote session connecting to my NixOS session with: Mouse/Keyboard -works perfectly Xbox Controller -nothing works Steam Controller -only navigating steam overlay works, KDE controller options display inputs, but game doesn't detect anything
okaaaaay soooo I've got a workaround but it confuses me extremely. I noticed that when I rearrange controller order that my remote play partner could suddenly control the game, but I couldn't anymore. So now I plugged in a 2nd controller on my side and rearranged the controllers until it suddenly worked, I was able to play with my friend, but had a 2nd controller just by the side doing nothing. so yeah weirdest workaround, really not sure what's going on here.
I just tried remote play and had this error when trying without a controller: ! Does anyone have any ideas for a proper solution? ping as someone who might use :man_shrugging:
i do use steam, but I don't use remote play :(
I marked this as stale due to inactivity. &rarr;
still important to me
I ran into this last week.
please test the PR
This should work if remote client has the correct udev rules installed. For Nixos, this is accomplished by doing or or . Edit:
I took that out for a spin, but no dice. Tried solution as well, but that doesn't seem to work either— it seems something about how Steam launches subprocesses (or our sandboxing infra) has changed since then. This does resolve the error, but now there's this even more mysterious one in its place: What does work, however, is moving to , and putting a script in its place that prefixes with and chainloads. I'm definitely not familiar with how steam works internally, but I did snoop through its processes and found env vars and that are absent of our additional paths. Obviously, replacing files managed by Steam isn't really an option, but I hope this sheds a little more light on the problem. I will note that even after all of this, I'm still not getting more than a [non-game, generic steam] loading screen— playing around with the firewall suggests that it actually needs more ports to be open than are documented. That belongs in another issue, though, and we can get to that once everyone can actually launch this at all.
thanks for looking into this. Yea, unfortunately I don't have a directory on my system, so I'm not really in a position to test this further. This may only be populated if you use the service. But I don't see the harm in adding additional paths to which may be empty for some individuals, the linking logic should just move on to the next paths. :(
seems potentially related— if this is true, setting env vars like we are currently won't help for subprocesses at all, as they only affect Steam itself. :( I assume this is done to avoid user-set environment variables from causing havoc with games (e.g. libraries needed to run Steam may not be what you want to load into a specific game, if it requires a specific version of SDL, etc). I'm not sure how to go about solving this, as it may require changes to Steam as well.
Actually, found this which looks suspiciously like the issue we're having. I'll see if I can test whatever beta has the purported fix later & report back.
We also set to , as some zachtronics games did the scrubbing as well.
Steam is definitely not respecting those: checking the env vars from doesn't show our changes, and they differ from . I'm fairly sure its subprocesses are then taking from these 'cleansed' variables.
The actual problem was a lot sillier: our Steam runtime version is out of date by 3.5 months. What made debugging this much more difficult was the fact that Steam downloads a copy of it as well, which is what I thought it was loading in— that copy did have the necessary symbols, etc.
is there some way automatic steam runtime updates could be PR'd by a bot so this doesn't happen again in the future?
I think that would require removing the on ?
I already the ability for it to be able to update itself in I just forgot about only caring about packages that it can query through :)

Discussion:
pname = "steam-runtime"; # from https://repo.steampowered.com/steamrt-images-scout/snapshots/ <del> version = "0.20201203.1"; </del> <ins> version = "0.20210317.0"; </ins> src = fetchurl { url = "https://repo.steampowered.com/steamrt-images-scout/snapshots/${version}/steam-runtime.tar.xz"; <del> sha256 = "sha256-hOHfMi0x3K82XM3m/JmGYbVk5RvuHG+m275eAC0MoQc="; </del> <ins> sha256 = "061z2r33n2017prmhdxm82cly3qp3bma2q70pqs57adl65yvg7vw"; </ins> name = "scout-runtime-${version}.tar.gz"; };