Open farmaazon opened 2 months ago
Official release build also fails for me.
SO suggestion also does not apply as I cannot pass --no-sandbox
:
> ./enso-linux-x86_64-2024.4.1-rc3.AppImage --no-sandbox
Registering protocol client.
The single argument '--no-sandbox' does not denote a readable file: Error: ENOENT: no such file or directory, access '--no-sandbox'
Checking if '--no-sandbox' denotes a URL to open.
The single argument '--no-sandbox' does not denote a valid URL: TypeError: Invalid URL
Unknown argument: sandbox
Enso 2024.4.1-rc3 command line interface.Usage: enso [options]
Both single-dash and double-dash prefixes are accepted for all options. For instance, the help message can be displayed by entering either '--help' or '-help'. The '-no-' prefix may be utilized to disable a specific option. For example, to connect to the application from a web-browser, the creation of a window can be suppressed by entering either '-window=false' or '-no-window'.
Suggestion - allow for --no-sanbox
to be passed to AppImage
and then dropped from Enso parameters. We could even limit this to a specific OS.
I am on Ubuntu 24.04 as well and have not experienced this. I remember though that I have installed some system package (via sudo apt-get install ...
) to support any AppImage execution. I don't remember configuration any sandbox stuff.
I am on Ubuntu 24.04 as well and have not experienced this. I remember though that I have installed some system package (via
sudo apt-get install ...
) to support any AppImage execution. I don't remember configuration any sandbox stuff.
Maybe you are referring to libfuse2
. Yes, that's normal and I have it installed.
Note: I added an option to pass --no-sandbox
so at least we have a hack to make it start.
Also, this appears to be a problem with every AppImage since that version of Ubuntu. So maybe the workaround is an acceptable solution for now.
From @hubertp
It prevents app from starting