-
Notifications
You must be signed in to change notification settings - Fork 86
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
Native Brigador fails to launch on KDE Wayland #636
Comments
Is Fedora still patching SDL 2 to make it default to native Wayland? The upstream default for SDL 2 is to prefer X11 via Xwayland. Using native Wayland for game windows triggers other issues, such as ValveSoftware/steam-for-linux#8020. If that guess is correct, a possible workaround is to set the game's launch options in Steam to It looks as though this particular game is using GLEW, which hasn't had significant updates since 2017, and assumes that OpenGL on Linux should always use GLX, which is an X11-specific protocol. This is not compatible with using a version of SDL that defaults to native Wayland and therefore does not create an X11 window. When the Steam Runtime gets a version of SDL that is strictly newer than the one in Fedora (likely to happen somewhat soon because SDL 2.30.0 is on the way), that would probably also work around this, by preferring the Steam Runtime's version of SDL over Fedora's.
That's consistent with what I've said above. When you use the Steam Linux Runtime compatibility tool, you're getting a version of SDL 2 from (a later branch of) the Steam Runtime, and not Fedora's version.
That's also consistent with what I've said above.
This surprises me. Is it creating an X11 window or a Wayland window in this case? |
@kisak-valve, please could you tag this as a game-specific issue? This isn't really a Steam Runtime bug, as such: as far as I can see, the Steam Runtime isn't doing anything specifically wrong here, it just isn't working around this particular game's limitations. |
Looks like yes: https://src.fedoraproject.org/rpms/SDL2/blob/rawhide/f/SDL2-2.0.22-prefer-wayland.patch.
Please try that. |
The output still doesn't mention either x11 or wayland, but it's using the generic x11 icon for the panel entry. Launching through steam without Steam runtime forced with |
What do you mean by "without Steam runtime forced"? Do you mean: Properties -> Compatibility -> uncheck "Force use of..."? Or something else?
Do you mean: Properties -> Compatibility -> "Force use of..." -> "Steam Linux Runtime 1.0 (scout)"? Or something else? (The reason I ask for clarification is that all Steam games are normally run via some sort of version of the Steam Runtime, but that might be either the Steam Linux Runtime container or the older LD_LIBRARY_PATH runtime.) |
Yes to both. |
A future version of SDL2 will automatically switch to X11 if it detects that the application is linked to GLEW (libsdl-org/SDL#8812) which I believe should solve this for you. |
Good to know. |
It looks as though maybe it has a bundled version of SDL which is used when you run it outside Steam, but is not used when running within Steam? When running it outside Steam, your log says:
and that version is far too old to have any concept of Wayland, which accidentally works around the limitation. |
Oh, I didn't notice that. But when I force the scout runtime without launch options and it successfully launches, the log lists the same linked version as when it crashes without scout forced:
|
Yes, except no :-) It's the same upstream release, but compiled differently. When you're forcing Steam Linux Runtime 1.0 (scout) (which is a Steam Runtime 2 (soldier) container plus some ABI-compat glue for the default When you're using the default |
Your system information
steamapps/common/SteamLinuxRuntime/VERSIONS.txt
?: 0.20230928.0steamapps/common/SteamLinuxRuntime_soldier/VERSIONS.txt
?: 0.20231107.66294steamapps/common/SteamLinuxRuntime_sniper/VERSIONS.txt
?: 0.20231107.66301Please describe your issue in as much detail as possible:
Not sure if this is the right place to report this.
When attempting to launch the native version of Brigador on a Wayland session, it fails to create the window and quits. Game log.
Checking the force compatibility checkbox and selecting Steam Linux Runtime (scout) allows the game to launch.
Switching to an x11 session allows the game to launch without forcing compatibility.
However, launching the game outside of Steam through a terminal on Wayland works.
I last played Brigador in October, but it ran on Wayland through Steam without changing compatibility.
Steps for reproducing this issue:
The text was updated successfully, but these errors were encountered: