Antigravity crashes on Linux, but works on Windows

Continuing the discussion from AntiGravity Review:

{
“isRemote”: false,
“systemInfo”: {
“operatingSystem”: “linux”,
“timestamp”: “2025-11-20T10:50:02.882Z”
},
“extensionLogs”: [
“2025-11-20 16:19:23.546 [info] FATAL ERROR: This binary was compiled with aes enabled, but this feature is not available on this processor (go/sigill-fail-fast).”,
“2025-11-20 16:19:27.143 [info] (Antigravity) 2025-11-20 16:19:27.142 [INFO]: Language server killed with signal SIGILL”,
“2025-11-20 16:19:27.172 [info] (Antigravity) 2025-11-20 16:19:27.158 [ERROR]: Failed to start language server: Error: Language server exited before sending start data”,
“2025-11-20 16:19:27.183 [info] (Antigravity) 2025-11-20 16:19:27.181 [ERROR]: LS startLanguageServer error: Language server exited before sending start data”
],
“mainThreadLogs”: {
“artifacts”:
},
“recentTrajectories”:
}

Summary:
On my dual-boot laptop (Windows + Linux), the Antigravity application works normally on Windows, but on Linux it fails to open. The application does not launch and appears to crash immediately without showing any UI.

Device Setup:

  • System: Dual-boot (Windows + Linux) on the same laptop

  • Windows: Antigravity works perfectly, no crashes

  • Linux: Antigravity fails to open / crashes on launch

Issue Details:

  • Attempting to launch Antigravity on Linux results in no window appearing.

  • No visible error message is shown on screen.

  • The same hardware runs the application flawlessly under Windows, ruling out device/hardware issues.

  • Issue seems to be specific to the Linux build/environment.

Expected Behavior:
Antigravity should open normally on Linux just like it does on Windows.

Actual Behavior:
Antigravity doesn’t open on Linux and appears to crash on startup.

Request:
Please investigate the Linux compatibility or provide troubleshooting steps. Let me know if logs or system details are required — I can share them.

1 Like

I have go the same issue. The Agent is not able to start. Please check the attached screenshot.

Other Info:
Debian Trixie (Gnome/Wayland)
Processor is old but VS code runs fine, so it should work.

Let me know if you guys want any other info.?

Best,
Vikas

1 Like

grep -i avx /proc/cpuinfo
grep -i aes /proc/cpuinfo

can you share info - what exactly CPU you have ?
i had same problem on VM/proxmox (lmde7).. → core when was trying to run AG
cpu switch to “host” type resolve problem

1 Like

It’s an old one. but vscode and chrome runs fine in wayland.
System Details Report


Report details

  • Date generated: 2025-12-08 02:24:34

Hardware Information:

  • Hardware Model: ASUSTeK COMPUTER INC. X553MA
  • Memory: 8.0 GiB
  • Processor: Intel® Pentium® N3530 × 4
  • Graphics: Intel® HD Graphics (BYT)
  • Disk Capacity: 500.1 GB

Software Information:

  • Firmware Version: X553MA.214
  • OS Name: Debian GNU/Linux 13 (trixie)
  • OS Build: (null)
  • OS Type: 64-bit
  • GNOME Version: 48
  • Windowing System: Wayland
  • Kernel Version: Linux 6.17.8+deb13-amd64