-
Notifications
You must be signed in to change notification settings - Fork 137
Description
Issue troubleshooting has identified that the issue is with Antigravity. To the Google Project IDX / Cloud Code Engineering Team,
I am reporting a critical failure in the Antigravity extension running on a Raspberry Pi (ARM64 architecture) with Debian 12 (Bookworm). The system binary is correctly installed via the official APT repository and functional, but the VS Code extension fails to activate or utilize the system executable, resulting in a persistent crash loop.
- Environment Details
OS: Debian GNU/Linux 12 (bookworm) aarch64
Hardware: Raspberry Pi (ARM64)
GLIBC Version: 2.36 (Compatible)
Installed Package: antigravity (version 1.104.0) installed via https://us-central1-apt.pkg.dev/projects/antigravity-auto-updater-dev/
System Binary Status: The command /usr/bin/antigravity --version executes successfully in the terminal, returning version 1.104.0 (arm64).
-
The Issue Despite the valid system installation, the IDE extension fails to start the language server. It appears to ignore the system path or fails to handshake with the pre-installed binary. Consequently, the extension fails to register its commands, rendering the editor unusable for AI workflows.
-
Error Logs Upon initialization, the Runtime Status reports "Not yet activated" and the following errors appear:
Antigravity server crashed unexpectedly. Please restart to fully restore AI features. Menu item references a command 'antigravity.importAntigravitySettings' which is not defined in the 'commands' section. Menu item references a command 'antigravity.importAntigravityExtensions' which is not defined in the 'commands' section.
- Attempted Workarounds (Failed) I have attempted the following troubleshooting steps without success:
Clean reinstallation via apt remove and rm -rf ~/.gemini/antigravity.
Manual creation of symlinks from /usr/bin/antigravity to ~/.gemini/antigravity/server.
Forcing configuration via "antigravity.binaryPath": "/usr/bin/antigravity" in settings.json.
Conclusion The extension logic on Linux ARM64 is defective regarding binary detection. It does not correctly respect the system installation provided by your own APT repository. I request an urgent fix to the extension's activation logic to properly bind to /usr/bin/antigravity on ARM systems.