SUMMARY RDP session shows a permanent white screen on the client when three monitors are enabled on a Plasma 6 Wayland session. Disabling an extra monitors avoids the issue (works with 2 or 1, doesnt matter which ones I keep enabled). Feature request: add an option to expose only the primary display (or select displays) to the RDP session. STEPS TO REPRODUCE 1.Start a Wayland session on KDE Plasma. 2.Enable System Settings → Remote Desktop → RDP server (default port 3389). 3.Have three monitors enabled (I tasted with the following): Dell Inc. DELL AW2518HF — 1920×1080 LG Electronics 23EA63 — 1920×1080 Fujitsu Siemens Computers GmbH E19W-5 — 1440×900 4.Connect from an RDP client to the machine. OBSERVED RESULT The RDP client connects but only displays a white screen. No desktop content appears. input works. EXPECTED RESULT The remote desktop should render normally. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 6.4.5 KDE Frameworks Version: 6.19.0 Qt Version: 6.10.0 Kernel Version: 6.17.4-4-cachyos (64-bit) Graphics Platform: Wayland GPU: AMD Radeon RX 6600 XT CPU: AMD Ryzen 7 5800X3D RAM: 32 GiB Tested with various RDP clients like Remmina 1.4.41, Windows RDP client on win 11, etc. ADDITIONAL INFORMATION Suspect interaction between kwin’s RDP/screencast path (PipeWire) and multi-output capture. Suggested feature: In Remote Desktop -> RDP, add “Share only primary display” or “Select displays to share.” This would also serve as a practical workaround for this bug while also being a useful feature to have. I don't expect many people to actually remote into there workstations from another workstation with 3 monitors so this doesn't really need a proper fix if we can't find the cause.
There is a codepath in ffmpeg which has to flip when dealing with a texture bigger than 4096 pixels. It's more likely to be that rather than the number of screens. In theory it should fallback to a software encoder. The other option we have in theory with RDP is to send multiple streams, but I don't know how good client support for that is.
Can you run krdp with QT_LOGGING_RULES="kpipewire_vaapi_logging.debug=true;kpipewire_logging.debug=true;kpipewire_libav_logging.debug=true" krdpserver you might need to stop the existing server.
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.
Created attachment 187085 [details] QT_LOGGING_RULES="kpipewire_vaapi_logging.debug=true;kpipewire_logging.debug=true;kpipewire_libav_logging.debug=true" krdpserver Tested with a 2560x1440 and 1920x1080 screen, problems still the same, whitescreen or crash. sometimes client manages to display a few frames. QT_LOGGING_RULES="kpipewire_vaapi_logging.debug=true;kpipewire_logging.debug=true;kpipewire_libav_logging.debug=true" krdpserver Operating System: Arch Linux KDE Plasma Version: 6.5.3 KDE Frameworks Version: 6.20.0 Qt Version: 6.10.0 Kernel Version: 6.17.8-2-cachyos (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800X3D 8-Core Processor Memory: 96 GiB of RAM (94,2 GiB usable) Graphics Processor: AMD Radeon RX 6600 XT