Rubin
Published
Native Linux executable does not run, exits with exit code 53
I've been trying to get the linux-native executable(s) for this game running on modern Linux (i.e., Linux 6.12.x, Wayland, etc). I've tried both the i386 and x86_64 binaries. In both cases the game crashes immediately. Checking the exit code on console (echo $?) I see that the binary exits with exit code 53.
Running the game with gdb I see the following:
Program received signal SIGTRAP, Trace/breakpoint trap.
__pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=5, no_tid=no_tid@entry=0) at pthread_kill.c:44
44 return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO (ret) : 0;
If you force this (linux native, oh the irony) game to run it's Windows variant, by forcing it to use Proton, the game runs flawlessly.
First start, the screen immediately backgrounded. After foregrounding the app, the screen was heavily glitched and unreadable. Starting the game a second time worked immediately, with no artifacts whatsoever.
The native Linux binaries of this game don't work on modern Linux systems (I've made a previous report about that, they exit with exitcode 53 almost immediately). Simply going to "Properties" -> "Compatibility" and enabling "Force the use of a specific Steam Play compatibility tool" and selecting "Proton Experimental" made the game work.
Runs perfectly, native Linux binaries, no Proton needed!
No tweaking needed, no Proton needed, runs linux-natively, ran immediately without issues.
The first two times I started the game, I didn't hear audio. For some reason, the third time and all times afterwards, I did and sound seems to be working normally.
When running in 8K resolution (which looks gorgeous by the way, especially the grass), the game frequently crashes (i.e., within minutes) with the following error:
d3d11.dll caused an Access Violation (0xc0000005)
in module d3d11.dll at 0023:78f1aa00.
When I play in 4K or less, the game seems much more stable (tested for 30 minutes, no crashes - previous crashing happened within 2 or 3 minutes every time).
When I tried to launch with Proton Experimental, after the intro-logos, when the first logo of the game shows, it tries to switch the resolution or it looks like it tries to maybe play some content, but immediately crashes to desktop. With GE-Proton9-22 this did not happen and I could launch the game succesfully and play (tested for about 20 minutes).
No special steps required, everything just worked as soon as I selected Proton Experimental in the compatibility tab of the game properties window.
