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

[Linux] - Cannot launch on MX linux 18 (Debian) #163

Open
dalerka opened this issue Jun 5, 2020 · 5 comments
Open

[Linux] - Cannot launch on MX linux 18 (Debian) #163

dalerka opened this issue Jun 5, 2020 · 5 comments
Labels
awaiting triage Needs debugging to know the root cause

Comments

@dalerka
Copy link

dalerka commented Jun 5, 2020

How can I fix this?
Following instructions here, but the program doesn't start (nothing happens) and same with clicking on the appImage file.

System info:

Host: mxs Kernel: 4.15.0-1-amd64 x86_64 bits: 64 compiler: gcc v: 6.3.0
Desktop: Xfce 4.12.3 tk: Gtk 2.24.31
Distro: MX-18.3_x64 Continuum March 14, 2018

Starting from the Terminal shows:

 $ ./ResponsivelyApp-0.1.6.AppImage             
[19177:0605/104044.027211:FATAL:setuid_sandbox_host.cc(157)] 
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 /var/tmp/.mount_Responn5a9re/chrome-sandbox 
is owned by root and has mode 4755.

##  adding `--no-sandbox` halts with:

 $ ./ResponsivelyApp-0.1.6.AppImage --no-sandbox
Gtk-Message: 10:43:46.517: GtkDialog mapped without a transient parent. This is discouraged.

and throws a JS error (in UI):
Uncaught Exception: Error: EACCES: permission denied, open...

However, running as root gets the program to launch (but only with --no-sandbox flag):

 $ sudo ./ResponsivelyApp-0.1.6.AppImage
[16654:0605/100646.244827:FATAL:electron_main_delegate.cc(211)] 
Running as root without --no-sandbox is not supported. See https://crbug.com/638180.
[1]    16653 trace trap  sudo ./ResponsivelyApp-0.1.6.AppImage
FAIL

 $ sudo ./ResponsivelyApp-0.1.6.AppImage --no-sandbox
(electron) The default value of app.allowRendererProcessReuse is deprecated, it is currently "false".  
It will change to be "true" in Electron 9.  For more information please check 
https://github.com/electron/electron/issues/18397
10:07:12.591 › Checking for update
10:07:12.762 › Generated new staging user ID: 63c084b6-c973-5bd4-947b-ce3c7e0c357a
10:07:14.640 › Update for version 0.1.6 is not available (latest version: 0.1.6, downgrade is disallowed).
10:07:14.642 › checkForUpdatesAndNotify called, downloadPromise is null

And thanks for sharing your awesome work! :)

@manojVivek manojVivek added the awaiting triage Needs debugging to know the root cause label Jun 5, 2020
@jjavierdguezas
Copy link
Contributor

Maybe this is related to this electron/electron#17972

@jjavierdguezas
Copy link
Contributor

@dalerka
Copy link
Author

dalerka commented Jun 6, 2020

@jjavierdguezas Thanks!
I looked into those issues, but I couldn't locate the "chrome-sandbox" in order to apply the chown + chmode commands.
The location suggested in the error message is temporary.
You need to make sure that /var/tmp/.mount_Responn5a9re/chrome-sandbox

So, I'm not sure what to do now. Also, how safe would it be to run such app as root and with --no-sandbox?

@jjavierdguezas
Copy link
Contributor

@dalerka sorry I'm not a linux expert but what I understood from those links (and others) is that this is an electron/electron-builder issue, it is not specific to ResponsivelyApp. The option to apply chown + chmode is when the issue occurs with some lib in development (the node_modules is right there), not when the final package has been created. The solution could be the patching one mentioned in those links: unpacking the AppImage, applying the changes and packing it back. If that solution really works, maybe @manojVivek could apply it in every release

@dalerka
Copy link
Author

dalerka commented Jun 8, 2020

@jjavierdguezas no worries, and thank you for taking time to look into the issue!
I can wait for the next release :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting triage Needs debugging to know the root cause
Projects
None yet
Development

No branches or pull requests

3 participants