[Feature] Linux support

[retarpt]

Please add support for Linux!

Update by @andrewpareles: the Linux download is available here! https://github.com/voideditor/binaries/releases

[rz-x]

Is it in the plans at this point?

[blooalien]

Please add support for Linux!

Yeah, that was the first thing I looked for, too. Been playin' with (and rather enjoying) Zed editor lately, and saw this on HackerNews and thought to myself "Neat! Another LLM-supporting editor / IDE alternative to play with!" Nope. Not yet, at least... 😢

Second thing I looked for (and happily found pretty much immediately) was Ollama (and other local LLM runner like vLLM) support for easy use of private local LLMs on machines with beefy enough hardware to run such things... 😁

[Shinoa-Fores]

The Linux AppImage is laughably broken, spitting out /tmp/.mount_Void-<ID>/AppRun: line 10: /usr/share/void/void: No such file or directory

Can be coaxed to work from sources, but far too much hassle atm.

[andrewpareles]

Would love some help on this. I spent a few days rebasing from VSCode/VSCodium build pipeline to get this working, but looks like deb works, but AppImage doesn't.

[Shinoa-Fores]

Would love some help on this. I spent a few days rebasing from VSCode/VSCodium build pipeline to get this working, but looks like deb works, but AppImage doesn't.

Will see what I can brew up over the weekend, because I'm on Gentoo Linux I need and overlay for node-gyp to get it to work so will report back if anything shakes out.

[micisse]

Ubuntu is a little recalcitrant with .AppImage. For all those who have or have had problems (with *.AppImage on linux). I recommend you use a “.desktop”. Follow these steps:

• Download the appropriate .tar.gz file (here https://github.com/voideditor/binaries/releases), and choose the version that corresponds to your machine

• Unzip and place it wherever you like... For example, I have it here /opt/void
• Create a file /usr/share/applications/void.desktop and here are its contents

Replace only /opt/void/bin/void with your bin path. You can also automate it with a script. The *.tar.gz version comes with its dependencies, unlike the AppImage version. I also recommend an icon: uncomment the corresponding line

Name=Void
Comment=Void is an open source Cursor alternative.
GenericName=Text Editor
Exec=/opt/void/bin/void --no-sandbox %F
TryExec=/opt/void/bin/void
# Icon=/opt/void/void.png
StartupWMClass=void
StartupNotify=true
Terminal=false
Type=Application
Categories=Utility;TextEditor;Development;IDE;
MimeType=application/x-void-workspace;
SingleMainWindow=true
X-GNOME-SingleWindow=true
Actions=new-empty-window;
Keywords=void;

[Desktop Action new-empty-window]
Name=New Empty Window
Exec=void --new-window --no-sandbox %F
# Icon=/opt/void/void.png

• Once all that's done, you'll have Void in your applications, so all you have to do is click to open it.

[Shinoa-Fores]

@andrewpareles managed to get this to build fine locally by adding the above mentioned items. Startup bitched at me over "safeStorage.encryptString" but this an upstream vscode thing iirc, easily bypassed using the --password-store=basic arg (for now).

[andrewpareles]

Thanks for the investigation @micisse and @Shinoa-Fores. I'm going to start linking people to this discussion.

If you're downloading Linux and have any issues with the steps above, feel free to continue this thread.

[dm17]

Will give it a try when there's a flatpak. Curious how different Void IDE is from running vim + ollama.

[yuceltoluyag]

https://aur.archlinux.org/packages/void-git

[andrewpareles]

@yuceltoluyag We didn't publish that; it's not an official binary.

[Freeshman]

I found a temporary way to run (ubuntu22.04):

1. ./xxxx.AppImage --appimage-extract
2. cd squarshfs-root/usr/share/void
3. ./void

[omidraha]

I successfully cloned and built the Void editor from the beta branch following the instructions. The React frontend builds fine, and the full project compiles without errors after running npm run buildreact and npm run compile.

I also tried downloading the beta.tar.gz release archive directly from GitHub, extracted it, and attempted to build from there. However, I encountered issues such as missing Git metadata causing postinstall scripts to fail, and similar problems running the Electron app.

Additionally, I tried running the AppImage from the release page:

https://github.com/voideditor/binaries/releases/tag/1.99.30034

Running the AppImage produces the following error:

./Void-1.99.30034.glibc2.29-x86_64.AppImage 
sed: /tmp/.mount_Void-1OuGCne/lib/x86_64-linux-gnu/libselinux.so.1: no version information available (required by sed)
/tmp/.mount_Void-1OuGCne/AppRun: 10: exec: /usr/share/void/void: not found

My system details:

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 24.04.2 LTS
Release:        24.04
Codename:       noble

It seems the AppImage's internal AppRun script tries to execute /usr/share/void/void which is not found inside the mounted environment.

I also tried extracting the AppImage, and the expected executable file is missing or misplaced.

---

Steps to reproduce:

1. Clone repo with: git clone --depth 1 --branch beta https://github.com/voideditor/void.git cd void

2. Install dependencies: npm install

3. Build React frontend: npm run buildreact

4. Compile full project: npm run compile

5. Run Electron app: npm run electron or npx electron build/lib/electron.js

---

Alternatively, downloaded and extracted the tarball from: https://github.com/voideditor/void/archive/refs/tags/beta.tar.gz Tried to build but encountered fatal: not in a git directory errors and others preventing build completion.

---

What happens:

• No window appears.

• No crash or detailed error messages on the console.

• When running npx electron build/lib/electron.js directly, I get GPU and sandbox errors like:

  The SUID sandbox helper binary was found, but is not configured correctly...
  Failed to get fd for plane.: No such file or directory (2)
  

• After fixing chrome-sandbox permissions and running with --no-sandbox --disable-gpu, Electron runs but still no window or output.

• Running the AppImage results in the error above about missing /usr/share/void/void.

---

Environment:

• OS: Ubuntu 24.04.2 LTS (or your distro/version)
• Node.js: v22.2.0 (also tested with Node 18 with same result)
• npm: latest
• Electron: 34.3.2 (installed locally via npm)
• Display: $DISPLAY=:0 (GUI environment is running)
• GPU: Using integrated Intel
• Running on physical machine

---

What I’ve tried:

• Running with --no-sandbox, --disable-gpu, --disable-software-rasterizer
• Fixing chrome-sandbox permissions (owned by root, mode 4755)
• Running under xvfb (virtual framebuffer) with xvfb-run
• Running Electron as root
• Testing a minimal Electron app (simple example works fine, Void editor does not)
• Checking for running Electron windows (ps aux | grep electron)
• Running with full debug environment variables (ELECTRON_ENABLE_LOGGING, etc.)
• Using Node versions 22 and 18
• Downloading and building from tar.gz release archive (encountered git directory related errors)
• Trying to run the official AppImage (encountered missing executable error)

[guyluz11]

Will give it a try when there's a flatpak. Curious how different Void IDE is from running vim + ollama.

Would love to see it as a Snap in the Snap Store. Will make the insulation easier.

[oech3]

https://github.com/voideditor/void/issues/503#issuecomment-2874032455

@andrewpareles We didn't publish that; it's not an official binary.

This is a build script using this repository, not a binary. However, it is not based on builds scripts from here currently...

There is also void-bin repacks .deb with system's electron.

[oech3]

Would you allow to use source=("git+https://github.com/voideditor/void.git#tag=${pkgver}") for unofficial source base distribution? Curreltly, #commit= is allowed only for versioned commit.

[ricardoamaro]

All the other editors are cross-platform. Not a good sign for its future if this editor starts without Linux support:

[sarahbx]

@ricardoamaro Linux binaries can be found here: https://github.com/voideditor/binaries/releases The OP had been updated.

But +1 be cool to see on the main page.

[ricardoamaro]

Correct. It should be showing on the main page. Hiding the open-source operating system from the main page seems like pushing it to the second league. At least since Void is also open-source should be teaming up with its ecosystem.