First issue is that you need to run sudo apt install libfuse2t64 to have AppImages running in your computer.
Then, you need an AppArmor policy to run Electron apps packaged as AppImage. The solution:
Save this in /etc/apparmor.d/cursor
# This profile allows everything and only exists to give the
# application a name instead of having the label "unconfined"
abi <abi/4.0>,
include <tunables/global>
profile cursor /home/bartmr/cursor.AppImage flags=(unconfined) {
userns,
}
Yes indeed you need you run sudo apt install libfuse2t64, but you don’t need to do the other stuff you mentioned. Instead, you can edit your .bashrc file to make a custom function, and then when you type cursor in the terminal, it would have the same effect as using the code terminal command from VS Code.
here’s the custom function i use, and it works perfectly in ubuntu24.04.
you could also make a .desktop file with similar parameters.
edit: forgot to mention you need to make the .AppImage executable first. this can be done using terminal or gui (right click > properties > toggle executable as program). this is a one time thing.
Still can’t login, even with --no-sandbox and --ozone-platform=wayland. Also, it is safer to allow user namespaces with AppArmor, than to disable the sandbox. The sandbox is what stops malicious iframes from running code that impacts the computer.
I completed the fuse install AND the apparmor parser instructions AND updated the permissions of the chrome-sandbox within the AppImage and repacked it. However, my error is still persistent and I can’t install Cursor on Linux ubuntu 24.04. Is there a way to install without no-sandbox
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
[79556:0828/094143.668380:FATAL:zygote_host_impl_linux.cc(202)] Check failed: . : Invalid argument (22)
I was able to get the problem rectified. It was a typo for the path in the apparmor profile. I am unsure if updating the permissions and repackaging the AppImage was necessary. It may be only the apparmor profile was but probably installing fuse was also.