Ubuntu - almost worked :)

[dnajd]

I ran your script and tried to run cursor, but nothing happened.. no output, anything?

Saw the file in /usr/local/bin/cursor was trying to call the AppImage.

Called the app image directly and got

dlopen(): error loading libfuse.so.2

AppImages require FUSE to run. 
You might still be able to extract the contents of this AppImage 
if you run it with the --appimage-extract option. 
See https://github.com/AppImage/AppImageKit/wiki/FUSE 
for more information

On Ubuntu

$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 24.04.2 LTS
Release:	24.04
Codename:	noble

I had to...

sudo apt update
sudo apt install fuse libfuse2

Still nothing.. running the app image directly I got

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
[57284:0327/160838.574015:FATAL:zygote_host_impl_linux.cc(207)] Check failed: . : Invalid argument (22)
Trace/breakpoint trap (core dumped)

Editing the /usr/local/bin/cursor, I added --no-sandbox and it finally worked.

[mablr]

Indeed, fuse is a necessary dependency for launching AppImage.

It seems that this problem has also been noticed here jorcelinojunior/cursor-setup-wizard#2.

I'll patch it later today.

[mablr]

After digging into the problem a bit, it seems that the installation of FUSE is quite difficult to automate seamlessly for any Debian-like distribution https://github.com/appimage/appimagekit/wiki/fuse. In this regard, the PR jorcelinojunior/cursor-setup-wizard#3 illustrates well how messy it is.

I see this script as a tool to simplify the appimage integration of Cursor. If Cursor fails to start due to lack of FUSE before using the installer, the installer will not solve the problem as it only deals with integration. So adding automated FUSE installation will probably not reduce the friction for Cursor appimage integration that much, while increasing the complexity of the script and making it harder to maintain.

Anyway, I think it would be useful to clarify this decision in the doc and in the output of the script.

[OriginalEXE]

For me the cursor command also does not work, until I add --no-sandbox, should that be the default?

[OriginalEXE]

I'm guessing this is needed because the script does not set up an apparmor profile, like https://github.com/jorcelinojunior/cursor-setup-wizard/ did?

[mablr]

Thanks, @OriginalEXE, for the clarification.

Instead of creating an AppArmor profile, it might be more relevant to add the --no-sandbox option. I believe this is a reasonable trade-off between security and compatibility across Debian- and Ubuntu-based distributions.

Let me know if you have any other suggestions.

[OriginalEXE]

👍🏻 Makes sense, I understand --no-sandbox is the more flexible solution