Flatpak (org.zdoom.GZDoom) Version 4.11.0 Crashes

[KW57]

Installing the Linux Mint Flatpak org.zdoom.GZDoom Version 4.11.0 crashes on launching doom. When launched I get a window with a message about submitting data to zdoom (for development purposes) but no matter what option I select (or if I just close the window), when the game actually launches I just get a black window and it locks up my desktop!

I rolled back the flatpak to version 4.9.0 and everything works fine.

System: Linux Mint 21.2 Cinnamon (vesion 5.8.4)
Linux Kernel: 6.2.0-33-generic
Processor: AMD Ryzen 5 5600G with Radeon Graphics × 6
Graphics: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne

[Jan]

FWIW I am having the same issue on 4.11 with the AUR compiled version on Arch Linux. Rollback to 4.10 fixes the issue.

My specs are
Kernel: 6.5.5-arch1-1
CPU: AMD Ryzen 9 5900X 12-Core Processor
GPU: Radeon RX 7900 XT

[Ludecan]

Also having the issue in Steam OS 3.5.
Seems to hang right before showing the main menu.

This happens both with and without mods (in Doom plutonia) and both if I accept or reject the data collection (which I intend to accept). Brutal Doom Platinum finishes loading it's progress bar and then hangs. Vanilla hangs without displaying anything.

I reverted to I think this commit https://github.com/flathub/org.zdoom.GZ ... e0a987ae99
(v4.10.0) And it's working now.

[Ludecan]

Bit of a newb with gzdoom in Linux and flatpaks in general but if there's a logfile I can send to help debug this lmk

[wildweasel]

The best I think you'd be able to get is to run the game from a terminal and copy out its output.

[Jan]

The best I think you'd be able to get is to run the game from a terminal and copy out its output.

As far as I can tell, it doesn't output any errors. It just hangs when trying to initialize video output:



I did find that the issue can be worked around by toggling the rendering API from OpenGL (the default) to Vulkan by setting the flag vid_preferbackend=1 in the config file. That's probably the best workaround for now.

[pbuyle]

I've had the same issue with both the Flatpak version and Ubuntu .deb package running on Pop! OS 22.04 . I confirm the vid_preferbackend=1 workaround.
I don't see anything helpful in it, but I attached the log.

[Blzut3]

Known issue: https://github.com/ZDoom/Raze/issues/966

It's almost certainly GZDoom/Raze tickling the ACO shader compiler in a way that's causing it to go haywire (which is to say this is almost certainly a bug in Mesa but I don't know specifically what the bug is). I don't know enough to comment more than that, but while the default would suggest otherwise the Vulkan backend is actually the backend you should be using anyway. So setting vid_preferbackend to 1 is actually a fix and not just a workaround.

[Graf Zahl]

Someone with access to an affected system will have to do some closer checks to see which change precisely triggers the compiler's misbehavior.
Also, has this been reported to the affected project so its maintainers can possibly do something about it? If we just silently work around the bug it won't help anybody.

[Blzut3]

The change has been bisected in the Raze ticket. If there's something I should try please let me know. Since I've never worked in this area I'm basically blind to narrow it down further.

I can open a ticket with Mesa, but it would be ideal if we knew precisely what's broken.

[Graf Zahl]

That doesn't really help because we still do not know what precise change in there makes it throw up.
Someone with access and some knowledge about shaders needs to run some checks. Without access to affected hardware it's hard to analyze.

[Jan]

So setting vid_preferbackend to 1 is actually a fix and not just a workaround.

The issue with that is that it's not the default and gzdoom will fail on a new install with the default config. It also fails before it gets the chance to create a new ini file, so on a new install you can't just go into the ini file to change the parameter and you have to do something like "gzdoom +vid_preferbackend 1" to get a working config in the first place.

Would it be an option to change the default backend from OpenGL to Vulkan?

[Rachael]

Would it be an option to change the default backend from OpenGL to Vulkan?

Done, though I wish this had come up before release so that we could've had this change in 4.11.0.