FA Forever client is unable to successfully start game itself

[nojusr]

Issue is exactly as the title suggests.

Exact package used: faf-client-bin.

I can confirm that I have run the setup script successfully, only noting that I was unable to use the non-legacy proton config wizard. I have also manually checked that every path provided by the setup script looks correct at a light glance.

Additionally, I can confirm that the game itself runs fine when launched through steam.

The only seemingly relevant logs are as follows (redacted for privacy). The game itself did not write any logs. (I have checked ~/.faforever/logs/game_*.log.

2024-04-24T16:38:40.800+03:00  INFO 265267 --- [FAF Client] [r-http-epoll-11] c.f.c.fa.ForgedAllianceLaunchService     : Starting Forged Alliance with command: [env, PROTON_NO_ESYNC=1, PROTON_NO_FSYNC=1, steam-run, %USER_PROFILE%/.local/share/Steam/ubuntu12_32/reaper, SteamLaunch, AppId=9420, --, %USER_PROFILE%/.local/share/Steam/ubuntu12_32/steam-launch-wrapper, --, /mnt/main/games/steam-games/steamapps/common/SteamLinuxRuntime_sniper/_v2-entry-point, --verb=waitforexitandrun, --, '/mnt/main/games/steam-games/steamapps/common/Proton, -, Experimental/proton', waitforexitandrun, %USER_PROFILE%/.local/share/faforever/bin/ForgedAlliance.exe, /init, init.lua, /nobugreport, /log, %USER_PROFILE%/.faforever/logs/game_22351835.log, /gpgnet, 127.0.0.1:34085, /mean, 1500.0, /deviation, 500.0, /savereplay, gpgnet://127.0.0.1:42635/22351835/XXXX.SCFAreplay, /country, XX, /numgames, 0, /numgames, 0] in directory: %USER_PROFILE%/.local/share/faforever/bin
pressure-vessel-wrap[400314]: W: Found more than one possible libdrm data directory from provider
2024-04-24T16:38:47.770+03:00  INFO 265267 --- [FAF Client] [onPool-worker-5] com.faforever.client.game.GameRunner     : Forged Alliance terminated with exit code 0

Additionally, experience suggests that the issue could have stemmed from running the game on a non-default steam library, but moving the game over from my HDD onto my boot drive, re running the setup script and trying again resulted in the exact same result.

I am at my wit's end here, I have no idea what's causing the issue and where to look further for any additional clues.