Open vanfanel opened 1 month ago
Sounds like an issue with direct scanout. Running sway with the environment WLR_SCENE_DISABLE_DIRECT_SCANOUT=1 will disable the feature and work around the problem. This is likely a bug with your video drivers. The last thing in the logs is direct scanout being entered right before sway is shutting down; although there are buffer allocations in between, I wonder why those are there (but those aren't going causing your bug).
Sounds like an issue with direct scanout. Running sway with the environment WLR_SCENE_DISABLE_DIRECT_SCANOUT=1 will disable the feature and work around the problem. This is likely a bug with your video drivers. The last thing in the logs is direct scanout being entered right before sway is shutting down; although there are buffer allocations in between, I wonder why those are there (but those aren't going causing your bug).
If it's my video driver (Intel, btw), why is Sway the only affected WLRoots compositor?
@Nefsen402 Also, setting WLR_SCENE_DISABLE_DIRECT_SCANOUT=1
does NOT work around the issue.
Another wlroots-based compositor where this bug is not present is Wayfire (https://github.com/WayfireWM/wayfire).
Sway Version:
Debug Log: swaylog.log
Configuration File: config.txt
Description: -Launch an SDL2 game, like Hydra Castle Labyrinth (https://github.com/ptitSeb/hydracastlelabyrinth) specifying fullscreen mode (-f) and keeping the desktop resolution (-d), as in:
hcl -f -d
-Watch the resulting black screen while the game is in fact running.Additional notes: -Other wlroots-based compositors don't have this issue (like labwc, where it runs fine), so it's not an wlroots problem. -Non wlroots-based compositors like Weston also don't have any problems with it.