[beta] remote play 'stream' fails to connect despite settings showing 'connected' to remote host

steamclosed Streaming

ValveSoftware/steam-for-linux#6283 · opened 2019-05-21 by craftyguy · updated 2019-12-06 · 16 comments · github

Ccraftyguy 2019-05-21 github

Your system information

Steam client version (build number or date): May 20 2019 @ 21:26:39
Distribution (e.g. Ubuntu): Arch Linux
Opted into Steam client beta?: Yes
Have you checked for system updates?: Yes

Please describe your issue in as much detail as possible:

When trying to stream a game from a remote system (same OS and steam client version), I receive an error that steam is unable to connect to the system. The 'remote play' section of the client settings shows that the remote system is found and available, but for some reason the IP it tries to use is 0.0.0.0 (obviously invalid). If I retry many times, it will eventually succeed. I have forwarded all ports listed here on the remote steam system's firewall.

Steps for reproducing this issue:

Start steam client on host and client systems
Verify that settings on client system 'sees' host:
Click 'stream' game on client system
Recieve this on the client system:

There is no relevant output on the host system, it seems like the client never contacts it.

Output from steam on the client system is here:

Installing breakpad exception handler for appid(streaming_client)/version(20190520212623)
Installing breakpad exception handler for appid(streaming_client)/version(1.0)
Installing breakpad exception handler for appid(streaming_client)/version(1.0)
Initializing player
Refresh rate: 60.00
Effective rate: 59.75
Video size: 1920x1080, output size: 1920x1080
Video rect: 1920x1080 at 0,0
Texture rect: 1920x1080 at 0,0
Initialized player
Connecting to server at address: 0.0.0.0:0
Session state Idle -> Connecting
Send to 0.0.0.0:0 with size 17 failed (22): 99<Ύ9<CStreamTransportClient stopping Remote Client service connection
Send to 0.0.0.0:0 with size 17 failed (22): Video size: 1920x1080, output size: 1920x1080
Video rect: 1920x1080 at 0,0
Texture rect: 1920x1080 at 0,0
Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Session state Connecting -> Idle

Jjdfalk 2019-06-03 github

Just an idea, does it work if you change it from beautiful to balanced? Seems stupid but I'm encountering close to the same issue and that seemed to be a work around until it can be fixed.

Jjohn5788 2019-06-14 github

I am seeing this issue as well as of the latest update that was pushed live today. I was using Remote Play last night just fine without any issues.

Initializing player Refresh rate: 144.00 Effective rate: 143.75 Video size: 1920x1080, output size: 1920x1080 Video rect: 1920x1080 at 0,0 Texture rect: 1920x1080 at 0,0 Initialized player Connecting to server at address: 0.0.0.0:0 Session state Idle -> Connecting Send to 0.0.0.0:0 with size 17 failed (22): ZF;�<P��CStreamTransportClient stopping Remote Client service connection Send to 0.0.0.0:0 with size 17 failed (22): Video size: 1920x1080, output size: 1920x1055 Video rect: 1876x1055 at 22,0 Texture rect: 1920x1080 at 0,0 Video size: 1920x1080, output size: 1920x1080 Video rect: 1920x1080 at 0,0 Texture rect: 1920x1080 at 0,0 Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Video size: 1920x1080, output size: 1920x1080

Mmcd1992 2019-06-15 github

Same issue here after last nights 'In-Home Streaming' to 'Remote Play' update.

CAPIJobRequestUserStats - Server response failed 2
Installing breakpad exception handler for appid(streaming_client)/version(20190614205209)
Installing breakpad exception handler for appid(streaming_client)/version(1.0)
Installing breakpad exception handler for appid(streaming_client)/version(1.0)
JS method call Messaging.PostMessage with 4 arguments
Initializing player
Refresh rate: 60.00
Effective rate: 59.75
Video size: 1920x1080, output size: 1920x1080
Video rect: 1920x1080 at 0,0
Texture rect: 1920x1080 at 0,0
Initialized player
Connecting to server at address: 0.0.0.0:0
Session state Idle -> Connecting
Send to 0.0.0.0:0 with size 17 failed (22): ��D���D��j���u����D��u��CStreamTransportClient stopping Remote Client service connection
Send to 0.0.0.0:0 with size 17 failed (22): Video size: 1920x1080, output size: 1920x1080
Video rect: 1920x1080 at 0,0
Texture rect: 1920x1080 at 0,0
Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Video size: 1920x1080, output size: 1920x1080
Video rect: 1920x1080 at 0,0
Texture rect: 1920x1080 at 0,0
Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Send to 0.0.0.0:0 with size 17 failed (22): Session state Connecting -> Idle

EDIT:
Interesting when I turned the streaming_client into a wrapper script that added --debug to the call it seems to work all of a sudden now.

Installing breakpad exception handler for appid(streaming_client)/version(20190614205209)
Installing breakpad exception handler for appid(streaming_client.bin)/version(1.0)
Installing breakpad exception handler for appid(streaming_client.bin)/version(1.0)
JS method call Messaging.PostMessage with 4 arguments
Installing breakpad exception handler for appid(streaming_client.bin)/version(1.0)
Installing breakpad exception handler for appid(streaming_client.bin)/version(1.0)
libva info: VA-API version 0.39.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/i386-linux-gnu/dri/radeonsi_drv_video.so
libva info: va_openDriver() returns -1
Initializing player
Refresh rate: 60.00
Effective rate: 59.75
Video size: 1920x1080, output size: 1920x1080
Video rect: 1920x1080 at 0,0
Texture rect: 1920x1080 at 0,0
Initialized player
Server available at address: 192.168.2.2:27031
Connecting to server at address: 192.168.2.2:27031
Session state Idle -> Connecting
CStreamTransportClient stopping Remote Client service connection
Session state Connecting -> Handshake
Video size: 1920x1080, output size: 1920x1080
Video rect: 1920x1080 at 0,0
Texture rect: 1920x1080 at 0,0
Session state Handshake -> Authenticating
Got control packet k_EStreamControlServerHandshake
Session state Authenticating -> Negotiating
Got control packet k_EStreamControlAuthenticationResponse
Got control packet k_EStreamControlNegotiationInit
Session state Negotiating -> StreamStarting
Got control packet k_EStreamControlNegotiationSetConfig
Session state StreamStarting -> Streaming
Got control packet k_EStreamControlSetQoS
Got control packet k_EStreamControlSetTargetBitrate
Starting audio stream: frequency=48000, channels=2
Opened audio device: format=2, channels=2, frequency=48000
Initialized audio decoder: codec=3, sample rate=48000, channels=2
Got control packet k_EStreamControlStartAudioData
Got control packet k_EStreamControlSetSpectatorMode
Got control packet k_EStreamControlSetCaptureSize
Got control packet k_EStreamControlSetTitle
Got control packet k_EStreamControlSetIcon
Got control packet k_EStreamControlSetCursor
Got control packet k_EStreamControlSetActivity
Got control packet k_EStreamControlSetCursorImage
Video size: 1920x1080, output size: 1920x1080
Video rect: 1920x1080 at 0,0
Texture rect: 1920x1080 at 0,0
Got control packet k_EStreamControlSetCaptureSize
Got control packet k_EStreamControlSetTitle
Got control packet k_EStreamControlSetIcon
Got control packet k_EStreamControlSetActivity
Got control packet k_EStreamControlSetCursor
Got control packet k_EStreamControlSetCursorImage
Video size: 1920x1018, output size: 1920x1080
Video rect: 1920x1018 at 0,30
Texture rect: 1920x1018 at 0,0
Got control packet k_EStreamControlStartVideoData
Video size: 1920x1018, output size: 1920x1080
Video rect: 1920x1018 at 0,30
Texture rect: 1920x1018 at 0,0
Got control packet k_EStreamControlVideoEncoderInfo
ffmpeg verbose: Opened VA display via X11 display :0.0.
ffmpeg error: Failed to initialise VAAPI connection: -1 (unknown libva error).
CVAAPIAccel: av_hwdevice_ctx_create() failed
libavcodec software decoding with 4 threads
ffmpeg verbose: Reinit context to 1920x1024, pix_fmt: yuv420p
Got control packet k_EStreamControlSetCursor
Video size: 1920x1018, output size: 1920x1080
Video rect: 1920x1018 at 0,30
Texture rect: 1920x1018 at 0,0
Marking frame 1 complete with status k_EStreamFrameResultDroppedLate
Got control packet k_EStreamControlSetCursorImage
Sending HID device 256c/006e/0   at 0005:0004:00
Sending HID device 256c/006e/1   at 0005:0004:01
Sending HID device 256c/006e/2   at 0005:0004:02
Sending HID device 046d/c332/0   at 0002:0003:00
Sending HID device 046d/c332/1   at 0002:0003:01
Sending HID device 2516/0011/0   at 0002:0002:00
Sending HID device 2516/0011/1   at 0002:0002:01
Got control packet k_EStreamControlSetTargetBitrate
Video size: 1920x1018, output size: 1920x1080
Video rect: 1920x1018 at 0,30
Texture rect: 1920x1018 at 0,0
Marking frame 55 complete with status k_EStreamFrameResultDroppedLate
Got control packet k_EStreamControlSetCursor
Got control packet k_EStreamControlSetCursor
Marking frame 57 complete with status k_EStreamFrameResultDroppedLate
Marking frame 58 complete with status k_EStreamFrameResultDroppedLate
Marking frame 59 complete with status k_EStreamFrameResultDroppedLate
Marking frame 60 complete with status k_EStreamFrameResultDroppedLate

Ccraftyguy 2019-06-15 github

Interesting when I turned the streaming_client into a wrapper script that added --debug to the call it seems to work all of a sudden now.

Does it reliably work for you? The issue is intermittent, so it has been hard for me to find any workarounds for it since sometimes it'll go several starts without any problem. If using --debug works reliably, then I'd bet money this is some sort of timing/race condition. Unfortunately the steam client is closed-source, so we're left speculating and hoping Valve notices this issue and pays attention, and cannot do anything else to help.

Mmcd1992 2019-06-15 github

It's sporadic for me too unfortunately. It's something in steam itself though with how it calls the streaming_client binary. Running streaming_client.bin with --gameid 15502218691512107008 --server 0.0.0.0:27031 --transport k_EStreamTransportUDP --quality 3 --captureres 0x0 tokenid

If steam is calling it with --server 0.0.0.0 it fails, somehow playing with it from other machines / phone it gets fixed and will start getting called with the proper LAN address. Running streaming_client.bin with --gameid 15502218691512107008 --server 192.168.2.2:27031 --transport k_EStreamTransportUDP --quality 3 --captureres 0x0 tokenid

Ttechb 2019-06-16 github

@mcd1992 can you share how you did the wrapper script? I'm having the issue, it's not intermittent, it just doesn't work at all.

Mmcd1992 2019-06-16 github

It's nothing that should fix the bug, it just shows what steam is passing to the streaming_client.

I just renamed my streaming_client to streaming_client.bin and replaced it with this:

#!/bin/bash

echo "Running streaming_client.bin with $@"
exec /home/unknown/.local/share/Steam/ubuntu12_32/streaming_client.bin "$@"

If steam is constantly trying to run it with --server 0.0.0.0 then it should be possible to use parameter expansion to replace the address with a static IP to your PC (untested, not sure how to do it exactly either).

EDIT:
Here's a quick script to strip out the --server parameter and let you set it to whatever you want. Also I despise bash scripting, no clue how it manages to make such simple tasks so difficult.

#!/bin/bash

UBUNTU32_DIR="$( cd "$( dirname "$0" )" && pwd )"
STREAMING_BIN=streaming_client.bin
SERVER=192.168.2.2:27031

for arg do
  shift
  [ "$arg" = "--server" ] && continue
  [ "$arg" = "0.0.0.0:27031" ] && continue
  set -- "$@" "$arg"
done

echo "Running $UBUNTU32_DIR/$STREAMING_BIN with $@"
exec $UBUNTU32_DIR/$STREAMING_BIN --server $SERVER "$@"

Jjohn5788 2019-06-16 github

@mcd1992 Your workaround seems to be working for me. I'm using this for now until an official fix is released.

Ttechb 2019-06-16 github

I'm getting "Authentication Failed" trying the work-around. Also beware, if steam has an update you'll need to redo the work-around.

Llawremi 2019-06-16 github

That might be because it happened to pass the correct IP that time and thus the replacement broke the call.

This script might be more robust:

#!/bin/bash

UBUNTU32_DIR="$( cd "$( dirname "$0" )" && pwd )"
STREAMING_BIN=streaming_client.bin
SERVER=10.0.1.180

ARGS=$(echo "$@" | sed "s/0.0.0.0/$SERVER/")

echo "Running $UBUNTU32_DIR/$STREAMING_BIN with $ARGS"
exec $UBUNTU32_DIR/$STREAMING_BIN $ARGS

Ttechb 2019-06-19 github

I've tried the script multiple times with no luck. It's now crashing the laptop, the screen will go black and instead of the pop saying "Couldn't connect to remote pc", it just crashes and throws me back to the login page for the laptop or just freezes everything and I have to do a hard reset.

Every time I start Steam again, it overwrites the scripts anyway. I've tried putting both computers back to not opt-in to the beta, and both being opted in and a mix of the two. I've disabled firewalls, disabled any anti-virus, made sure the pc was discoverable and anything else that might be doing it. Everything I've tried just isn't working and am just going to give up.

Llawremi 2019-06-19 github

The overwriting the scripts is probably (and unfortunately) unavoidable. The crashing of the desktop might be a different problem.

Ccraftyguy 2019-06-19 github

You can try making the file immutable (chattr +i path/to/wrapper), but that might cause steam to fail in new ways when it can no longer overwrite that file (or maybe it'll Just Work? I haven't tried it)

Ddmp1ce 2019-06-19 github

@techb The script @lawremi created works for me. I also have to replace the script from time to time. Probably when I restart steam. Make sure you put in the correct IP address for your server.

Ttechb 2019-11-01 github

This issue seems to have been patched, I haven't had problems for a couple weeks now. Some games require me to try it a few times before it'll work, but the vast majority of games work fine.

The issue where I have to try it a few time, only on specific games, I think is because the game sometimes take a while to load and the stream sees it as no activity and terminates early. I think anyway.

The only other issue, that I found a solution for, is if the UAC stuff, prompts for admin rights, will break the stream. Removing the check in the checkbox "Run as Administrator" in the exe's compatibility settings resolves it.

Kkisak-valve maintainer 2019-12-06 github

Closing per the last comment.

Nothing extracted yet.