Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to run appimage #165

Open
inorick opened this issue Mar 18, 2021 · 4 comments
Open

Unable to run appimage #165

inorick opened this issue Mar 18, 2021 · 4 comments
Labels
bug Something isn't working installation Issue when trying to install the software linux Issue related to a Linux OS

Comments

@inorick
Copy link

inorick commented Mar 18, 2021

I get the following error when trying to run the 0.2 appimage:

$ chmod +x liground-0.2.0-linux.AppImage 
$ ./liground-0.2.0-linux.AppImage 
[2321:0318/193941.884527:FATAL:setuid_sandbox_host.cc(158)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /tmp/.mount_ligrouupWnPY/chrome-sandbox is owned by root and has mode 4755.
Trace/breakpoint trap
@QueensGambit
Copy link
Collaborator

QueensGambit commented Mar 18, 2021

Hello @inorick ,
can you give information about your operating system and if release 0.1.0 has been working?

The problem you have run into seems to be a known problem when trying to run electron-js applications on ArchLinux:

@QueensGambit QueensGambit added bug Something isn't working installation Issue when trying to install the software linux Issue related to a Linux OS labels Mar 18, 2021
@inorick
Copy link
Author

inorick commented Mar 18, 2021

Release 0.1.0 gives me the same problem. I am running Debian 10.

@inorick
Copy link
Author

inorick commented Mar 18, 2021

Ok, so I found this bug report that mentions Debian 10 specifically:
cryptoadvance/specter-desktop#769
It references this comment from an electron bug:
electron/electron#17972 (comment)
I suspect that Debian's kernel does not enable unprivileged access to CLONE_NEWUSER.
Running the app image with --no-sandbox allows me to start both release 0.1 and 0.2. Although the solution is of course not ideal.

@QueensGambit
Copy link
Collaborator

Thank you for pointing out an interim solution and I agree that adding --no-sandbox is not ideal for security reasons.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working installation Issue when trying to install the software linux Issue related to a Linux OS
Projects
None yet
Development

No branches or pull requests

2 participants