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

[Mai_Trung_Dat]

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?

[Botspot]

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.