[Bug Report] "Antigravity server crashed unexpectedly" on Linux ARM64 (Ubuntu via Proot)

Google Antigravity
1

Description: I am attempting to run the Antigravity desktop application on a Linux ARM64 environment. While the main editor window (UI) launches successfully, the AI Agent/Backend fails to initialize, resulting in a persistent crash loop.

Environment:

Device Architecture: aarch64 (ARM64)

OS: Ubuntu 22.04 LTS (Running via Proot/Termux on Android)

Software Version: Antigravity 1.16.5 (Installed via .deb)

Installation Method: apt install ./antigravity…deb

Symptoms:

The application launches successfully with --no-sandbox.

The “Quota Monitor” initially reports: Systems offline. Could not detect Antigravity process.

Shortly after, a red error popup appears:

“Antigravity server crashed unexpectedly. Please restart to fully restore AI features.”

The Agent status indicator remains in a loading/crashed state.

Logs & Errors Observed: When running from the terminal, I observe the following critical errors:

Keyring Error (Even with basic store enabled): You’re running in a GNOME environment but the OS keyring is not available for encryption.

Process Crash: The output indicates that the internal language server or agent process terminates immediately upon launch.

Troubleshooting Steps Attempted (None resolved the issue): I have tried the following configurations to rule out environment issues, but the Server Crash persists:

Flags: Running with --no-sandbox, --disable-gpu, and --user-data-dir=/root/.config/…

Password Store: Added --password-store=“basic” to bypass the GNOME Keyring dependency.

Dependencies: Fully installed all required libraries (libnss3, libatk, libasound2, libgbm1, etc.).

Permissions: Ensured all files in /usr/lib/antigravity and /usr/bin/ have executable permissions.

Conclusion: It appears there is a binary incompatibility with the Agent’s backend process (possibly related to TCMalloc or specific syscalls) on the ARM64 Linux architecture, specifically within a Proot environment.

Request: Could the team investigate the ARM64 build stability? Alternatively, is there a “Lite Mode” flag to disable the heavy local agent processes so the editor can still be used for basic tasks?

Screenshot_2026-02-09-21-22-38-053-edit_com.termux.x11
Screenshot_2026-02-09-21-22-38-053-edit_com.termux.x111080×1248 158 KB

2

I fixed this issue with a QEMU system VM that runs the language_server_linux_arm as PID 0 with a compatible kernel with the needed 48-bit address space. All communication (stdin, stdout, and the various FIFOs and sockets) between the binary and the host environment is plumbed by network sockets and port forwarding.

This was necessary to get Antigravity running on Raspberry Pi boards, all of which ship 39-bit address space kernels except for the Raspberry Pi 5’s 16k pagesize kernel. My implementation uses KVM to minimize emulation overhead. If your Android device does not expose /dev/kvm, it should be fairly simple to change the qemu-system-aarch64 command to not use KVM. Just thought I’d leave this here in case it would help someone. (Or run ARM64 Debian/Ubuntu on your phone and simply use the Pi-Apps appstore inside of it, that should work too)

Here’s the link to the script: pi-apps/apps/Antigravity/install-64 at master · Botspot/pi-apps · GitHub

If you have any questions/improvements, feel free to open an issue or PR on my repo.

3

there is a lite mode I’m using, with remotessh development.

Then, antigravity, same as it’s parent vscode, is opening all the files and extensions on a remote computer, accessible with ssh, probably even google cloud console. remote ports are redirected, so even web programming may be done.

4

[Help] Antigravity AI Server Crash loop on Ubuntu 24.04.4 LTS - Ryzen 5 3500U

Body:

I’m running Antigravity IDE on Ubuntu 24.04.4 LTS and I’m stuck in a persistent “Server Crashed” loop. It works fine on my Windows partition, so it’s a Linux-specific configuration issue.

System Specs:

  • OS: Ubuntu 24.04.4 LTS (Noble Numbat)

  • Kernel: 6.17.0-14-generic

  • CPU: AMD Ryzen 5 3500U (AES-NI and SVM confirmed ENABLED in BIOS and lscpu)

  • IDE Version: 1.21.6 (apt install)

The Specific Error: Launching with --verbose reveals that the Extension Host fails to start the AI server:

  • [ERROR]: Language server exited with code 2

  • [ERROR]: Failed to start language server: Error: Language server exited before sending start data

What I’ve already tried:

  1. Verified BIOS settings (SVM is ON).

  2. Set kernel.apparmor_restrict_unprivileged_userns=0.

  3. Raised fs.inotify and ulimit file descriptor limits.

  4. Cleared ~/.config/Antigravity/ and killed all zombie processes.

  5. Launched with --no-sandbox and --disable-gpu.

It seems like the antigravity-agent binary is dying immediately. Has anyone solved this specific “Code 2” exit on Noble? Is there a missing dependency (like libssl1.1) or a specific AppArmor profile I need to tweak?

5

Title: [SOLVED] Antigravity AI Server “Code 2” Crash on Ubuntu 24.04 (Ryzen 3000/3500U)

If you are running Antigravity IDE on Ubuntu 24.04 (Noble Numbat) with a Ryzen 3000-series CPU and getting a persistent “Server Crashed Unexpectedly” loop, I’ve found the root cause and the fix.

The System Context

  • Machine: HP EliteBook 745 G6

  • CPU: AMD Ryzen 5 3500U (Zen+)

  • OS: Ubuntu 24.04.4 LTS (Noble Numbat)

  • Kernel: 6.17.0-14-generic

  • IDE Version: 1.21.6

The Problem

The IDE UI loads, but the AI agent crashes immediately. Running the binary at /usr/share/antigravity/resources/app/extensions/antigravity/bin/language_server_linux_x64 manually reveals the true error:

CRNGT failed. SIGABRT: abort

crypto/internal/boring._Cfunc__goboringcrypto_RAND_bytes

The “Why”: The AI language server is compiled with BoringCrypto. This library performs a strict “Continuous Random Number Generator Test” (CRNGT) on the CPU’s hardware entropy. Certain Ryzen 3000/3500U chips have a known firmware bug with the RDRAND instruction that fails this check. BoringCrypto treats this as a security failure and kills the process (SIGABRT).

The Solution

You must mask the RDRAND capability at the OpenSSL/BoringSSL level and bypass the Ubuntu 24.04 AppArmor “sandboxing” for unprivileged user namespaces.

1. The Fix (Terminal)

Launch the IDE with this specific capability mask:

Bash

export OPENSSL_ia32cap="~0x4000000000000000"
antigravity --no-sandbox

Note: The bitmask $~0x4000000000000000$ specifically tells the software to ignore Bit 62 (RDRAND) and fall back to software-based entropy.

2. Make it Permanent (.bashrc)

To ensure every terminal session has the fix:

Bash

echo 'export OPENSSL_ia32cap="~0x4000000000000000"' >> ~/.bashrc
source ~/.bashrc

3. Fix the Desktop Launcher (App Menu)

Ubuntu 24.04’s security layer requires this flag even when launching from the GUI. Edit your .desktop file:

sudo nano /usr/share/applications/antigravity.desktop

Update the Exec lines to:

Exec=env OPENSSL_ia32cap="~0x4000000000000000" /usr/bin/antigravity --no-sandbox %U

After saving, update your database: sudo update-desktop-database