Zettlr: Linux Install Issues

Created on 30 Mar 2019 · 20Comments · Source: Zettlr/Zettlr

Description

Install issue. Seems to be related to electron?
Nothing happens when trying to open normally.
From the terminal reveals this:
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 /opt/google/chrome/chrome-sandbox is owned by root and has mode 4755.

If you sudo chown and then sudo chmod to fix this, it seems to work then.

Expected behaviour

Install and work simply as previous versions did.

Platform

OS: Arch (Previous versions worked fine and should be the same here)
OS Version Kernel 4.19.30
Zettlr Version 1.2.1

bug [non-critical] confirmed external Issue

Source

j-proc

👍1

Most helpful comment

@samarulmeu Thx for the info.

If it's only an issue on Arch based systems, a workaround is acceptable. Just as a note to any devs that come across this, you can feel free to close the issue if you prefer not to support arch based distros.

I can confirm that
sudo chown root /opt/Zettlr/chrome-sandbox & sudo chmod 4755 /opt/Zettlr/chrome-sandbox
fixes this issue on arch based distros and allows it to run.

j-proc on 31 Mar 2019

👍2

All 20 comments

Yup, I'm getting the same thing and I just pulled 1.2.2.

I experienced this two days ago and was waiting till the weekend to double check. I'm on Antergos (which is basically Arch). I have cleared out node_modules and rerun npm i (to no avail).

jcuenod on 30 Mar 2019

Try the sudo fix? Can anyone on a Debian based distro verify. This really shouldn't be distro dependent as it's a very basic functionality.

j-proc on 30 Mar 2019

On Ubuntu I had no problem. I am currently running 1.2.2

samarulmeu on 31 Mar 2019

Maybe this is related to Zettlr currently using Electron 5 beta …?

nathanlesage on 31 Mar 2019

@samarulmeu Thx for the info.

I can confirm that
sudo chown root /opt/Zettlr/chrome-sandbox & sudo chmod 4755 /opt/Zettlr/chrome-sandbox
fixes this issue on arch based distros and allows it to run.

j-proc on 31 Mar 2019

👍2

@j-proc Thanks for the confirm!

I prefer to also support Arch based distributions … but if it's an issue with either electron-builder or Electron … is there already an issue open?

nathanlesage on 31 Mar 2019

I'll try to look into that. Just from some Googling that was a guess. But I
suppose I could look into the build scripts to see where it comes from. You
can mark it appropriately in the meantime and I'll try to get back to you.

On Sun, Mar 31, 2019, 3:08 PM Nathan LeSage notifications@github.com
wrote:

@j-proc https://github.com/j-proc Thanks for the confirm!

I prefer to also support Arch based distributions … but if it's an issue
with either electron-builder or Electron … is there already an issue open?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Zettlr/Zettlr/issues/134#issuecomment-478370863, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AtK7cbHoSSo1hpeOv2Ie0PlWDK5HLIOWks5vcQe9gaJpZM4cT48c
.

j-proc on 31 Mar 2019

👍1

I can confirm the sudo fix does work (I'm running a clone of the repo so it's the chrome-sandbox in ./node_modules/electron/dist/chrome-sandbox).

jcuenod on 2 Apr 2019

👍1

Same issue on debian buster.
Fix works here as well.

TriciaHampton on 2 Apr 2019

👍1

Perhaps chown/chmod in postinstall script of deb package to work around.

TriciaHampton on 2 Apr 2019

👍1

Alright, the electron builder docs on this are virtually nonexistent, but I'll give it a try. So please stay tuned for a beta including this fix. I can't test it locally, so I appreciate any testing help with this!

nathanlesage on 2 Apr 2019

@nathanlesage https://github.com/electron/electron/pull/17269 seems to be part of addressing it.

I don't do much with electron, so I haven't actually followed on how electron-build is seperate. https://github.com/electron/electron/issues/16631#issuecomment-476082063 is essentially the same as @TriciaHampton suggested, their suggestion is this.

And I guess this isn't arch specific. I'm not sure why ubuntu would avoid it. But until the external issue is fixed, it seems a patch as they suggested is a good option.

j-proc on 2 Apr 2019

Electron Builder is successfully running chmod 4755 on the chrome sandbox, so it seems to work. New release due this afternoon, including the fix! Please comment whether or not it works, so that we can close the issue, eventually!

nathanlesage on 5 Apr 2019

👍1

Hmm, that didn't seem to do the trick for me...

I'm still getting the .../dist/chrome-sandbox is owned by root and has mode 4755. error.

jcuenod on 5 Apr 2019

mh … I wonder if I could chown root and whether this would make sense. Or probably we'll just hope for electron 5 to solve this problem …

nathanlesage on 6 Apr 2019

My vote would be to wait for electron 5 before doing something like that...

jcuenod on 8 Apr 2019

Alright, it should be right around the corner if nothing goes wrong with the Electron-Team. Let's hope sooner than later!

nathanlesage on 8 Apr 2019

It was already possible to package compatible with suid sandbox deb/pacman builds using electron v5 beta releases and it's possible now with v5.0.0. See more info here.