46.8/9 fail to start on Ubuntu 24.04 LTS

Bug Reports
1

Recently got updated to 46.9, and then when I tried again got 46.8. Both don’t run with the same error:

The setuid sandbox is not running as root. Common causes:
  * An unprivileged process using ptrace on it, like a debugger.
  * A parent process set prctl(PR_SET_NO_NEW_PRIVS, ...)
Failed to move to new namespace: PID namespaces supported, Network namespace supported, but failed: errno = Operation not permitted
[3632280:0307/150949.859626:FATAL:zygote_host_impl_linux.cc(201)] Check failed: . : Invalid argument (22)
Trace/breakpoint trap (core dumped)

The appimage is: Cursor-0.46.8-be4f0962469499f009005e66867c8402202ff0b7.deb.glibc2.25-x86_64.AppImage

The previous one 46.9 I deleted, but had the same issue.

My working app image is cursor-0.45.14x86_64.AppImage which Cursor pulled in by itself on a restart. (I was unable to use that method to update to 46.8, and had to go to the changelog page.)

I’ve never had this issue with Cursor before, so not sure what the problem is.

2 Likes
2

Same issue on my side with Ubuntu 24.04 LTS as well.

3

I am having the same issue with Ubuntu 24.

I found this post from last year for a different application:
https://discuss.saleae.com/t/linux-version-does-not-launch-on-just-released-ubuntu-24-04-lts/2866

Basically a workaround is to run cursor.AppImage with the --no-sandbox flag

4

To keep running in sandbox (i.e. not using --no-sandbox):

# replace with current build
chmod +x Cursor-0.46.11-ae378be9dc2f5f1a6a1a220c6e25f9f03c8d4e19.deb.glibc2.25-x86_64.AppImage
# Extract to squashfs-root
./Cursor-0.46.11-ae378be9dc2f5f1a6a1a220c6e25f9f03c8d4e19.deb.glibc2.25-x86_64.AppImage --appimage-extract
# Fix sandbox permissions
sudo chmod +s squashfs-root/usr/share/cursor/chrome-sandbox
sudo chown root:root squashfs-root/usr/share/cursor/chrome-sandbox

After this, Cursor can be launched with squashfs-root/AppRun.

They have moved chrome-sandbox from squashfs-root/chrome-sandbox to squashfs-root/usr/share/cursor/chrome-sandbox since 0.45.

5

Problem still exists on 47.7. Please fix this so I don’t have to have a special launch config for Cursor.