Repository navigation
[Bug] Plasmazones being active prevents "direct scanout" mode for fullscreen or borderless fullscreen applications #1169
Replies: 2 comments 1 reply
|
Thanks for the detailed report and the repro steps, they made this quick to track down. PlasmaZones was the cause. The daemon keeps one transparent, full-screen overlay surface per monitor that the OSD, layout picker, zone overlay and snap assist all draw into. It stayed mapped on the overlay layer for as long as the daemon ran, so it sat above every window, fullscreen ones included. KWin only scans out a fullscreen window when nothing visible is stacked on top of it, so that idle overlay forced compositing on every monitor. That's why stopping the daemon fixed it. The fix in #1170 takes the overlay down whenever nothing is showing on it, and puts it back when an OSD or overlay actually appears. If you can build from source, I'd appreciate a check on your setup, since I could only verify it in a nested KWin session, which has no real display planes: Then restart the daemon (or log out and back in) and run your If building isn't convenient, the fix will be in the next release. On borderless windowed games that fill the screen without being real fullscreen: with "Show border" on, PlasmaZones draws its border around them, and that also forces compositing. A rule with the "Exclude from decorations" action matching the game avoids it. |
|
Fixed in 3.5.4 (#1170). The overlay is taken down once nothing is showing on it, so fullscreen windows can go straight to the display again. Thanks for testing it. The borderless windowed idea is a separate request, so feel free to open it as its own idea. Closing this, but reply here if you still see it on 3.5.4. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Description
With plasmazones enabled, direct scanout doesn't activate for fullscreen or borderless windowed but fullscreen applications.
Direct scanout is a mode where kwin directly passes through the swapchain image buffer of the fullscreen window to the display/hardware directly, without compositing. This reduces latency and improves performance.
Expected Behavior
I expected plasmazones to not cause direct scanout issues or disable whatever causes direct scanout issues when a window is fullscreen or a borderless window fills the entire screen.
Steps to Reproduce
qdbus org.kde.KWin /Effects org.kde.kwin.Effects.toggleEffect showcompositingmpv --no-config --fullscreen --vo=gpu-next --hwdec=auto-safe "av://lavfi:color=c=black:s=1920x1080:r=60:d=60"which plays a generated black video stream for 60 seconds, fullscreen.If at step 8. it still shows the red border, some other overlay application or setting is blocking direct scanout.
Heres what to check if direct scanout is not working even with plasmazones daemon disabled:
KWIN_DRM_NO_DIRECT_SCANOUT=1is NOT set.report which cant be sent in the intended field: plasmazones-report-20261027-132232.tar.gz
PlasmaZones Version
cachyos/plasmazones 3.5.3-1
Display Server
Wayland
Desktop Environment
Plasma 6.8.1
Distribution
CachyOS
Support Report
Checklist
All reactions