Cursor Linux won't run due to sandbox issue

Bug Reports
1

Cursor on Linux doesn’t run on the first try.
You download it, type ./Cursor*.AppImage, you get this:

./Cursor-0.49.5-x86_64.AppImage 
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
[203003:0425/144824.318571:FATAL:zygote_host_impl_linux.cc(207)] Check failed: . : Invalid argument (22)
Trace/breakpoint trap (core dumped)

Being greeted with an error on the first try is not a great UX. The thing is, if you feed this into an LLM, it tells you the solution (–no-sandbox). Which suggests to me that Cursor could be a bit smarter about figuring out how to run itself.