https://bugs.kde.org/show_bug.cgi?id=527984
Zamundaaa <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED Latest Commit| |https://invent.kde.org/plas | |ma/kwin/-/commit/c9d720793b | |bcef9483ab290673032d39441c0 | |e6f --- Comment #7 from Zamundaaa <[email protected]> --- Git commit c9d720793bbcef9483ab290673032d39441c0e6f by Xaver Hugl. Committed on 29/10/2026 at 14:54. Pushed by zamundaaa into branch 'Plasma/6.8'. compositor: handle possibly missing render device Commit 6783f9610c moved the cross-GPU direct scanout check from backends/drm into the compositor, but dropped the null check on the render device. GpuManager's compatibleRenderDevice() returns nullptr for scanout devices that have no render device to pair with, such as evdi DisplayLink outputs. This caused deviceId() to be called on a null pointer whenever a buffer from another device is considered for direct scanout on such an output. On systems with a DisplayLink dock, this crashes kwin_wayland as soon as a fullscreen surface is shown on an evdi output. This change restores the previous behavior: If there is no compatible render device, treat the buffer as coming from another GPU and refuse direct scanout. (cherry picked from commit 43a74990f34159e68a12e85dc1ff1d9b0d908ee3) Co-authored-by: Fae Schiewe <[email protected]> M +1 -1 src/compositor.cpp https://invent.kde.org/plasma/kwin/-/commit/c9d720793bbcef9483ab290673032d39441c0e6f -- You are receiving this mail because: You are watching all bug changes.
