Portal backend service active: plasma-xdg-desktop-portal-kde.service
Please describe your issue in as much detail as possible:
Steam Remote Play becomes unusable when Steam is started with the -pipewire option on KDE Plasma Wayland.
The video stream shows frequent flickering that looks like stale/wrong frames are inserted between correct frames. It does not look like normal network packet loss, image corruption, or a completely jumbled stream. It looks more like the stream sometimes displays an older frame or wrong previous frame between current frames.
Important A/B results on the same host, same client, same network, same desktop session, and same game/application:
steam without -pipewire + software encoding:
works correctly
steam without -pipewire + hardware encoding:
works correctly
steam -pipewire + software encoding:
broken, stale/wrong frame insertion flicker
steam -pipewire + hardware encoding:
broken, stale/wrong frame insertion flicker
So this does not appear to be specific to hardware encoding. The issue appears tied to Steam Remote Play’s -pipewire capture path.
I also tested OBS on the same KDE Wayland session with Screen Capture (PipeWire) as the source and FFmpeg VAAPI H.264 as the video encoder. OBS records the desktop correctly with no stale-frame insertion or flickering.
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:
Start a KDE Plasma Wayland session on an Intel Arc Battlemage Linux host.
Start Steam with PipeWire capture enabled:
steam -pipewire
Start a Steam Remote Play stream from a client.
Enable the detailed performance overlay on the client if available.
Move the camera in a game or show other continuous motion on the host.
If the issue does not appear immediately, stop and restart the stream a few times. The issue is intermittent.
Observe that the client video sometimes flickers by inserting stale/wrong frames between correct frames.
Restart Steam without -pipewire and repeat the same test. The issue does not occur; both software and hardware encoding work correctly.
Your system information
1782437068xeAdditional relevant system information:
xdg-desktop-portal 1.22.1-2xdg-desktop-portal-kde 6.7.1-1pipewire 1:1.6.7-1wireplumber 0.5.15-1Portal backend service active:
plasma-xdg-desktop-portal-kde.servicePlease describe your issue in as much detail as possible:
Steam Remote Play becomes unusable when Steam is started with the
-pipewireoption on KDE Plasma Wayland.The video stream shows frequent flickering that looks like stale/wrong frames are inserted between correct frames. It does not look like normal network packet loss, image corruption, or a completely jumbled stream. It looks more like the stream sometimes displays an older frame or wrong previous frame between current frames.
Important A/B results on the same host, same client, same network, same desktop session, and same game/application:
So this does not appear to be specific to hardware encoding. The issue appears tied to Steam Remote Play’s
-pipewirecapture path.I also tested OBS on the same KDE Wayland session with
Screen Capture (PipeWire)as the source and FFmpeg VAAPI H.264 as the video encoder. OBS records the desktop correctly with no stale-frame insertion or flickering.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:
-pipewireand repeat the same test. The issue does not occur; both software and hardware encoding work correctly.