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

Gamescope quits on startup/splash screen close #1673

Open
3 of 6 tasks
EoceneMiacid opened this issue Dec 20, 2024 · 10 comments
Open
3 of 6 tasks

Gamescope quits on startup/splash screen close #1673

EoceneMiacid opened this issue Dec 20, 2024 · 10 comments

Comments

@EoceneMiacid
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Are you using any gamescope patches or a forked version of gamescope?

  • The issue occurs on upstream gamescope without any modifications

Current Behavior

Gamescope quits when a game's splash screen/popup window closes, making it unusable with games that have one. I seem to recall this worked fine before.

Good example is Helldivers 2, which shows the anticheat popup before it shows the window proper.

Steps To Reproduce

  • Launch gamescope with any game which shows a splash screen/popup window first (e.g. Helldivers 2)
    (gamescope -W 1920 -H 1080 -r 60 -f --force-grab-cursor -- %command%)
  • Observe gamescope shutting down after the splash screen closes.

Hardware information

- Distro: Arch Linux
- CPU: Ryzen
- GPU: Radeon
- Driver Version: 24.3.1

Software information

- Desktop environment: RDE
- Session type: Wayland
- Gamescope version: 3.16.1-1-g1c9495c3
- Gamescope launch command(s): -W 1920 -H 1080 -r 60 -f --force-grab-cursor

Which gamescope backends have the issue you are reporting?

  • Wayland (default for nested gamescope)
  • DRM (default for embedded gamescope, i.e. gamescope-session)
  • SDL
  • OpenVR

Logging, screenshots, or anything else

No response

@matte-schwartz
Copy link

I don't have Helldivers 2 to check, but I tried a few games with launchers that close themselves or anti-cheat windows that only pop up for a second or two and haven't been able to get this to happen yet on KDE Plasma Wayland w/ a 7900xtx. can you share any gamescope logs? and does it coredump if you check coredumpctl?

@layercak3
Copy link

layercak3 commented Dec 26, 2024

If nvidia is not involved and kwin or wlroots is in use, it may be the same as #1456 (comment), but more info is needed to tell.
I still don't understand why that issue only affects some people and not others.
Edit: If it does reproduce on DRM/SDL then this is definitely not the same issue, sorry. I'm also not interested testing these applications.

@Shinrafugitives
Copy link

I also get the same issue with this and Jojo's Bizarre Adventure: All-Star Battle. I've tried launching from both nested and embedded, so it's present in both Wayland and DRM. I've confirmed that both games' anticheat do work on linux, as they'll run without gamescope, but the latter won't run on gamemode through Hyprland without freezing.

@matte-schwartz
Copy link

Something else has to be going wrong here. I just tried the Jojo game on nested Wayland w/ Plasma 6 and also tried the DRM backend, and both worked without issue using gamescope version 3.16.1-1-g1c9495c3 (gcc 14.2.1) on Arch Linux. Also hearing that Helldivers 2 is working fine on another gamescope dev's setup, so I guess my immediate suspicions are either some kind of a build difference when packaging gamescope or a yet to be known distinguishing factor at runtime/an environment level

@ChthonVII
Copy link

Similar problem with Guild Wars, which has a splash screen. Gamescope just hangs without showing the splash screen. On any backend. Debian Trixie just upgraded to 3.15.13-2. It used to work in gamescope 3.11.49-1.

(Note: You do not need to buy Guild Wars to test this. You can download the client for free (here) and go as far as the login screen without buying an account.)

Even weirder, it's not working with Kate. Yes, Kate, KDE's plain old text editor. (I was using this for a sanity test.) Gamescope just dies on launch. Again, it used to work in gamescope 3.11.49-1.

@matte-schwartz
Copy link

matte-schwartz commented Dec 29, 2024

I'm unable to reproduce the issue in Guild Wars either after downloading the client and installing it, tested in both gamescope-session and gamescope nested on KWin Wayland. I chose Proton Experimental as my runner. At this point a bisect would be ideal, or any additional details you can provide about your setup and any ways it may differ from a "normal" setup. For example, my DE is Plasma 6.2.4 w/ KWin Wayland on Arch Linux using kernel 6.12.6 and Mesa 24.3.2 at the moment. I checked Mesa-git and that was also fine.

Separately, gamescope -- kate has been broken for a while now iirc, not sure it's related to this specific issue though.

@ChthonVII
Copy link

I'm using Wine-GE-Proton8-26. As I said, Guild Wars runs normally without gamescope, but with gamescope it just hangs without showing the splash screen.

After some further testing:

  • Merely setting the wine version to Proton Experimental via environment variables (no steam runtime) yields the same result as Wine-GE-Proton8-26.
  • Using Proton Experimental plus steam runtime-sniper makes gamescope work.

This is less than ideal, since Guild Wars has a lot of extras to install/inject that don't really work well via Steam's interface, and using steam runtime-sniper outside Steam is a large pain in the ass. I'd really like to know what component of the steam runtime is making this work, and if it's something that can be supplied without as much overhead.

Also, I'm getting a few pixels of white border on the right and bottom edges of the screen in fullscreen and borderless fullscreen with the default wayland backend. Changing to the sdl backend fixes it. Is this a known issue, or should I go open a ticket for it?

@matte-schwartz
Copy link

matte-schwartz commented Dec 30, 2024

the extra pixel border/scaling issue was fixed with #1630 in 3.16.1

@EoceneMiacid
Copy link
Author

EoceneMiacid commented Dec 30, 2024

Found some time to look into this a bit more.

Back 4 Blood shows an Easy Anticheat popup, and causes Gamescope to quit.
However, Halo The Master Chief Collection also shows this, but works fine.

When it fails (in B4B's case), gamescope outputs the following line:

[gamescope] [Error] xdg_backend: Compositor released us but we were not acquired. Oh no.

I tried a few different backends (sdl, wayland), but those fail straight away, i.e. they don't even show the anticheat popup.

Could this be compositor related? I use Wayfire.

@Delor3an91
Copy link

Hi,

Same problem here. Gamescope 3.16.1 broken.

Wish You well

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants