https://bugs.kde.org/show_bug.cgi?id=522901

--- Comment #4 from Jack <[email protected]> ---
Summary

When OBS records the primary monitor through the Wayland PipeWire screencast
portal while OBS is displayed on a secondary monitor, the captured video
develops persistent ghosting/stale frames after the desktop has been running
for several minutes.

The desktop itself renders correctly. The corruption is only present in the
captured stream.

GPU Screen Recorder does not exhibit the problem.

Hardware

GPU

NVIDIA RTX 5070

Driver

610.43.03

CPU

Intel i9-14900K

RAM

128 GB

Two identical monitors.

Software

Bazzite Fedora 44

Plasma 6.7.2

Wayland

OBS Studio

PipeWire

Steps to reproduce
Boot into Plasma Wayland.
Open OBS.
Place OBS entirely on the secondary monitor.
Record the primary monitor using PipeWire screen capture.
Continue using the desktop for several minutes.
Ghosting/stale image data begins appearing in the recording.

Moving OBS back to the primary monitor changes the behavior.

GPU Screen Recorder does not reproduce the issue.

Expected

Captured frames exactly match what is displayed.

Actual

Old frame contents remain visible in the captured stream.

The desktop itself does not visibly corrupt.

The corruption appears only in PipeWire screen capture clients.

Additional testing performed
OBS Flatpak
OBS native
OBS Safe Mode
Different encoders
PipeWire restart
WirePlumber restart
Portal restart
KDE updated to latest available
NVIDIA updated to latest available
VR headset disconnected
HDR disabled
Different OBS preview settings
Different monitor arrangements

No change.

GPU Screen Recorder works correctly.

Source investigation

Built KWin from source.

Investigated

src/plugins/screencast/screencaststream.cpp

Specifically explicit synchronization

supportsSyncObj
SPA_META_SyncTimeline

and damage tracking.

No obvious upstream fix found between Plasma 6.7 and master.

Suspected area

PipeWire screencast synchronization between KWin and NVIDIA when multiple
outputs are active.

The problem appears related to compositor capture timing rather than OBS
itself.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to