Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SDL2 games show black screen when running in fullscreen + keeping desktop resolution. #8161

Open
vanfanel opened this issue May 17, 2024 · 2 comments
Labels
bug Not working as intended

Comments

@vanfanel
Copy link

vanfanel commented May 17, 2024

  • Sway Version:

    • swaymsg version 1.10-dev-dcdb727 (May 17 2024, branch 'master')
  • 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.

@vanfanel vanfanel added the bug Not working as intended label May 17, 2024
@Nefsen402
Copy link
Contributor

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).

@vanfanel
Copy link
Author

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Not working as intended
Development

No branches or pull requests

2 participants