Trial Deployment of Linux Builds

Apologies it has taken this long, but we are now trialing linux build deployments. These builds are deployed untested. I have changed ⁠version-history on discord to now split out preparing the builds and deploying them. The windows build will now refuse to deploy a build that fails digital signature. Both builds will now indicate if they have successfully be deployed or not. The master server MAY indicate an incorrect build for linux, if linux fails to deploy. This will be changed soon when I can update that side of the deployment process.

You can download the trial builds for linux directly at:https://ksa-linux.ahwoo.com/

Please consider contributing​

It will increase our costs significantly to host this separate linux deployment. We are already spending x10 as much as we get in contributions - so it would make a great deal of help if folks who find the linux deployment useful consider contributing. If you do contribute - please do note in the contribution message if you can that it is FOR the linux deployments. I will use this data to help push that we should continue to integrate this going forward.

Report Linux issues​

Please discuss linux issues here and we will do our best to resolve them. One member of the team is developing on linux, so we do have some capacity to try and resolve these issues where they occur.

 

[Kiwi Shark]

Maybe by 'It will increase our costs significantly to host this separate linux deployment.' they meant the development cost, not the file host/upload cost, idk.

Terra Incognita on Discord said file delivery isn't that costly compared to the staffing necessary. It's a matter of labor involved with the extra development, testing, fixing, overhead, etc. more than actually providing the download.

 

[Psycho_zs]

A summary of current issues I observe as of v2026.2.38.3713:

• Requires libvulkan-dev (libvulkan.so instead of libvulkan.so.1)
• Poorly handles window resizes and fullscreen state change
• Missing window metadata (app-id, tags, parent)
• Unpredictably spawns windows.
  • a minor issue on Wayland in general
  • a major issue on tiling compositors specifically, exacerbated by lack of window metadata
  • need a killswitch/single-window mode
  • there is no positioning-that-should-not-be-named on Wayland (Absolute positioning. Shh... Wayland devs will curse you if they hear those words), so have to work around that, or check out zones protocol when/if it matures enough.
    • having properly tagged and parented windows will make it possible to do proper positioning from compositor's side with rules

 

[averageksp]

No issues so far for me with Linux. Amazing work at RocketWerkz and Ahwoo!