Package Details: antigravity 1.11.17-1

Git Clone URL: https://aur.archlinux.org/antigravity.git (read-only, click to copy)
Package Base: antigravity
Description: An agentic development platform from Google, evolving the IDE into the agent-first era.
Upstream URL: https://antigravity.google/
Keywords: ai-coding ai-ide antigravity editor google ide vibe-coding vscode vscode-fork
Licenses: LicenseRef-Google-Antigravity
Submitter: Doshiba
Maintainer: HurricanePootis (AlphaLynx)
Last Packager: AlphaLynx
Votes: 30
Popularity: 21.97
First Submitted: 2025-11-18 18:05 (UTC)
Last Updated: 2025-12-09 15:19 (UTC)

Latest Comments

1 2 3 4 5 6 Next › Last »

zebus3d commented on 2025-12-10 14:02 (UTC)

To close all processes for now, I am using killall antigravity, in case it is useful to anyone.

ArulGandhi commented on 2025-12-10 10:48 (UTC)

I can confirm that there are processes that don't close on their own. SIGSEGV is still happening after yesterday's update. I tried to kill the processes using pkill, which result in another SIGSEGV. Overall the package is not stable on Arch I'd say.

zebus3d commented on 2025-12-09 22:25 (UTC)

After closing Antigravity, there are still about 8 processes open. If I reopen Antigravity, new processes open and never close when I exit the program. Does this happen to anyone else? They have minimal network and hard drive activity.

clusterider commented on 2025-12-09 16:06 (UTC)

I am getting too much I/O usage even when running antigravity and also when i close it after running is there any quick fix for it?

dne commented on 2025-12-09 13:41 (UTC)

@lecooldudeujel @ArulGandhi I can confirm antigravity core-dumping after closing (also under arch though)

lecooldudeujel commented on 2025-12-08 06:54 (UTC)

I also had an issue with antigravity constantly spamming SIGSEGV for at least around 3 minutes after closing. Also, the agent is only able to read files from the scratch folder instead of the workspace. If anyone can confirm if they're Arch-only issues, it would be nice

ArulGandhi commented on 2025-12-06 16:41 (UTC)

@Zpecter Thanks for confirming. I'll have a look, it's likely due to some non-standard configurations I have.

jfc commented on 2025-12-06 16:28 (UTC)

I encountered a build failure during the package() phase where tar fails with: Cannot change ownership to uid 65534, gid 65534: Value too large for defined data type.

To fix this reliably for all users, I suggest adding the --no-same-owner flag to the extraction commands in the PKGBUILD. This forces the extracted files to be owned by the build user, preventing the overflow error.

Here is the suggested change:

1     if [ -f "data.tar.xz" ]; then
2         tar -xf data.tar.xz --no-same-owner
3     elif [ -f "data.tar.zst" ]; then
4         tar -xf data.tar.zst --no-same-owner
5     elif [ -f "data.tar.gz" ]; then
6         tar -xf data.tar.gz --no-same-owner
7     else
8         msg "Error: Could not find data.tar.* inside deb archive."
9         return 1

10 fi

Zpecter commented on 2025-12-06 10:30 (UTC)

@ArulGandhi, I'm also on latest arch and antigravity versions, and I don't have any SIGSEGV on closing.

ArulGandhi commented on 2025-12-06 10:27 (UTC)

Is anyone else getting a SIGSEGV everytime they close antigravity? I'm on latest arch, latest version of antigravity, only happens on closing.

1 2 3 4 5 6 Next › Last »