Latest linux build immediately throws an unhandled exception

Autumn :3

New Member
Mar 16, 2026
3
1

Game Version

2026.3.11.3916

Operating System

CachyOS, kernel 6.19.9-1-cachyos

What Happened​

Upon running the game from the terminal, it pretty much immediately returns an unhandled exception, doesn't even manage to open a window, or output anything other than the exception to the terminal before crashing.

What Was Expected​

The game running as normal.

Reproduction Steps​

  1. Run the game from the terminal. (Command: ./KSA)
  2. Game immediately returns the exception.

Reproduction Rate​

Always.

Additional Info​

Full contents of the exception are as follows:

Unhandled exception. System.ComponentModel.Win32Exception (13): An error occurred trying to start process '/home/autumnvleaves/Games/KSA/linux-x64/Brutal.Monitor.Subprocess' with working directory '/home/autumnvleaves/Games/
KSA/linux-x64/'. Permission denied
at System.Diagnostics.Process.ForkAndExecProcess(ProcessStartInfo startInfo, String resolvedFilename, String[] argv, String[] envp, String cwd, Boolean setCredentials, UInt32 userId, UInt32 groupId, UInt32[] groups, Int32
& stdinFd, Int32& stdoutFd, Int32& stderrFd, Boolean usesTerminal, Boolean throwOnNoExec)
at System.Diagnostics.Process.StartCore(ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
at Brutal.Monitor.Monitor.Start(String debugLogPath)
at Brutal.Monitor.Monitor..ctor(String debugLogPath)
at KSA.Program..ctor(IReadOnlyList`1 inArgs)
at KSA.Program.Main(String[] inArgs)
fish: Job 1, './KSA' terminated by signal SIGABRT (Abort)
 
Upvote 0
Executables do not have executable permissions in this archive, easy to fix:
chmod +x KSA Brutal.Monitor.Subprocess
 
This is because the file ./Brutal.Monitor.Subprocess also needs to be made executable, alongside ./KSA. Previously, all files in the archive were executable but with this release their permissions have been (correctly) dropped to 664.
The symlink for libvulkan.so still needs to be created manually after unpacking the archive. If you aren't aware, it needs to point to your system's file which for Debian based distros is /usr/lib/x86_64-linux-gnu/libvulkan.so.1.
 
Previously, all files in the archive were executable

Huh, I totally missed that. Would nag about it if I noticed )

The symlink for libvulkan.so still needs to be created manually after unpacking the archive. If you aren't aware, it needs to point to your system's file which for Debian based distros is /usr/lib/x86_64-linux-gnu/libvulkan.so.1.

Or install libvulkan-dev which contains libvulkan.so (also a symlink). Relying on a dev name for a library is a bug.
 
  • Like
Reactions: sleepy_eb and Grug