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

            Bug ID: 524011
           Summary: PipeWire screencast buffers corrupt on KWin/Wayland -
                    kpipewire does not seem to have sync support added by
                    KWin MR !6204
    Classification: Frameworks and Libraries
           Product: KPipeWire
      Version First 6.6.4
       Reported In:
          Platform: Kubuntu
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected]
  Target Milestone: ---

DESCRIPTION
krdp gives me a permanently blank screen (black in krdc, white in Remmina) when
connecting from another machine — no video ever arrives, though input works
fine (i can see the server scrolling in an editor when doing so on the client).
kpipewire's debug logging in krdpserver shows lots of "kpipewire_logging:
buffer is corrupt" messages.

STEPS TO REPRODUCE
 - On a Plasma Wayland session, start krdpserver (tried v6.6.4)
 - Connect an RDP client to the machine running krdpserver
 - Watch the logs with QT_LOGGING_RULES="kpipewire*.debug=true" set

OBSERVED RESULT
Every captured buffer is immediately flagged "buffer is corrupt".
kpipewire_record_framestatistics reports "Processed 0 frames" ~ every second,
indefinitely. 
This happens on both a real monitor (--monitor 0) and a freshly created virtual
output (--virtual-monitor 2560x1440@1), and is independent of the video encoder
(tried both VAAPI and forcing software libx264 via KPIPEWIRE_FORCE_ENCODER) and
independent of Nvidia driver version (tried 610.43.02 and 595.84, the latter
being Ubuntu's own recommended driver for this GPU).

EXPECTED RESULT
Valid frames reach the encoder and get sent to the client.

SOFTWARE/OS VERSIONS
Operating System: Kubuntu 26.04 LTS
KDE Plasma Version: 6.6.5
KDE Frameworks Version: 6.24.0
Qt Version: 6.10.2

ADDITIONAL INFORMATION
GPU: NVIDIA GeForce RTX 5060 Ti, driver 610.43.02 (also reproduced on 595.84).
Let me know if more information is needed.

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

Reply via email to