I initially thought it was just Proton games, but after trying to fix it from that angle for a while I found out that even native linux games running proton are failing to launch. I’ve already tried running AMD_VULKAN_ICD=RADV after finding out it could be something to do with AMDVLK vs RADV but that doesn’t seem to have fixed anything. Here’s all the relevant error logs
Both have WARNING: radv is not a conformant Vulkan implementation, testing use only. pop up multiple times, which I think it the main problem, but I have no idea what’s causing it.
For reference, vulkaninfo --summary gives this
[1112/150603:ERROR:sandbox_linux.cc(325)] InitializeSandbox() called with multiple threads in process gpu-process
[1112/150603:INFO:CONSOLE(0)] "The specified value '!' does not conform to the required format. The format is '#rrggbb' where rr, gg, bb are two-digit hexadecimal numbers.", source: file://localhost/home/daniel/.local/share/Steam/steamapps/common/Total%20War%20WARHAMMER/share/FeralUI/PGOW/Core/feralUI.html (0)
Installing breakpad exception handler for appid(gameoverlayui)/version(1.0)
[1112/150619:ERROR:gpu_watchdog_thread.cc(253)] The GPU process hung. Terminating after 10000 ms.
TotalWarhammer: dumped to "/home/daniel/.local/share/feral-interactive/Total War Warhammer/crashes/130acfe1-f439-b957-78ee4df3-0c55444c.dmp"
TotalWarhammer: crash reporter "/home/daniel/.local/share/Steam/steamapps/common/Total War WARHAMMER/bin/feral_linux_crash_reporter" launching
Game crashed, if possible email [support@feralinteractive.com] with the crash file [/home/daniel/.local/share/feral-interactive/Total War Warhammer/crashes/130acfe1-f439-b957-78ee4df3-0c55444c.dmp] and details
So the gpu process hung…
[1112/150619:ERROR:gpu_watchdog_thread.cc(253)] The GPU process hung. Terminating after 10000 ms.
You shoud be able to get more information by running:
sudo dmesg --follow
and then start Total War Warhammer again. There must be something printed which relates to this error.
That command really seems to dislike either my logitech keyboard or mouse, there were several thousand errors about that even though they work fine before I even launched the game, and only about a half-dozen lines about trying to launch it, here’s those lines
Here’s the pastebin of the whole thing as well, but most of it is just logitech-djreceiver 0003:046D:C537.0006: Unexpected input report number 128 repeated over and over again Pastebin
Kernel 5.13 is EOL to my knowledge. Might help to run newer kernel (such as 5.15) or a LTS kernel (such as 5.10).
All other than that, this problem is way over my knowledge.
Both commands render a cube, however it isn’t this game, it’s all games with vulkan, and by extension all proton games, so sending a dump log to Feral isn’t gonna do anything. The only reason I included the error from that specific game is because it’s the first one that came to mind that had a native vulkan version when I realized it might not be proton that was broken but vulkan as a whole. And I was running steam with runtime the whole time, I tried it again specifically enforcing it with your command but no dice.
I suppose if Vulkan works it could be steam? But I’ve reinstalled it twice, plus a couple native OpenGL games work fine with it, so I don’t understand how it could be that. I’m also gonna download another native vulkan game, I suppose it’s possible it’s just a problem with proton and Total War has a seperate, unrelated issue.
I did install another one and that one did work, so it appears it’s not a vulkan issue and the radv errors were red herrings, and Total war just happens to have an unrelated error.
Even further update, I’m just an idiot. It was an issue with the permissions from the NTFS drives I was mounting that most of my games were installed on, and I was just unlucky in the games that I decided to explicitly install on my ext4 drive, Total war had some unrelated issue and SCP Secret Lab had an update since I last played that broke proton compatibility, not only was there apparently never a vulkan issue, but there was also apparently never a proton issue, RIP the last couple days I spent trying to troubleshoot that
