I am experiencing the same issue on sway. It began happening very recently, and I have used remote play successfully many times in the past. For me, steam shows me playing the game, but the window never appears.
I am experiencing the same issue on Niri with a RTX 5060 TI. While trying to trouble shoot it, AI gave me this workaround:
#!/usr/bin/env bash
# 1. Grab the last streaming command from the log
RAW_CMD=$(grep -E "streaming_client" ~/.local/share/Steam/logs/gameprocess_log.txt | tail -n 1)
if [ -z "$RAW_CMD" ]; then
echo "No streaming log data found. Click 'Stream' in Steam first."
exit 1
fi
# 2. Strip hidden Windows carriage returns (\r) so bash can see the real end of the string
CLEAN_CMD=$(echo "$RAW_CMD" | tr -d '\r')
# 3. Extract from the binary path to the end of the line
ARGS=$(echo "$CLEAN_CMD" | grep -oP "'/home/jaopedrodev/.local/share/Steam/ubuntu12_32/streaming_client'.*")
# 4. Cleanly slice off the trailing log wrapper quote
ARGS="${ARGS%\"}"
# 5. Execute via the XWayland fallback path
eval "env -u WAYLAND_DISPLAY $ARGS"
It uses the streaming binary directly, passing the correct arguments that it grabs from steam logs.
I'm having the same issues in NixOS with an GTX 1650 on KDE Plasma Wayland. I got to stressed trying to fix it on Wayland (like with different configurations, beta clients or custom scripts), then tried on X11 Plasma and it works fine.
No ideia why, but it would make my day if someone fixed or even just discovered why this is happening on Wayland.
I am also on NixOS with a 3060 on sway. I also tried X11 and it worked fine there.
Any fix that isnt creating a script?
No fix yet, but I needed to use a slightly different set of ENV variables to get mine to work. I am on an RX 9070xt on nobara KDE, base kde window manager.
#!/bin/bash
LOGFILE="/home/lucinafailure/.local/share/Steam/logs/gameprocess_log.txt"
RAW_CMD=$(grep -E "streaming_client" "$LOGFILE" | tail -n 1)
if [ -z "$RAW_CMD" ]; then
echo "No streaming_client entry found."
exit 1
fi
CLEAN_CMD=$(echo "$RAW_CMD" | tr -d '\r')
FULL_CMD=$(echo "$CLEAN_CMD" | sed -E 's/.*tracked process "(.*)"/\1/')
if [ -z "$FULL_CMD" ]; then
echo "Failed to extract full command."
exit 1
fi
echo "Running:"
echo "$FULL_CMD"
echo
SDL_VIDEODRIVER=x11 \
EGL_PLATFORM=x11 \
env -u WAYLAND_DISPLAY \
bash -c "$FULL_CMD"
I can post the exact segfault message thing from kde I get if that helps.
SDL_VIDEODRIVER=x11x1 2026-07
Your system information
Please describe your issue in as much detail as possible:
I've started experiencing problems with steam remote play client (or streaming_client) since the start of May (possibly before)?
Upon accepting a remote play invite through my steam DMs I get a notification stating the streaming client has crashed.
The stack trace the notification provides stops at a function called "eglGetDisplay".
If I dig through gameprocess_log.txt and find the command steam tried to invoke streaming_client with then run it on my terminal it works perfectly fine and steam registers that I'm playing the game thats being streamed to me without any issues.
I've tried opting into the beta branch of steam however it did not fix the problem.
I've tried different DEs/WMs:
KDE (Walyand): Produces the described problem.
Hyprland (Wayland): Produces the described problem.
Sway (Wayland): Produces the described problem.
I3wm (x11): Remote play works without any problems.
Steps for reproducing this issue: