jitsi-meet-electron: Linux: 2.0.0 fails to start

[193209:0407/164939.241277: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 /tmp/.mount_jitsi-KCGvvK/chrome-sandbox is owned by root and has mode 4755.

I was a happy user of the previous version, but now it fails with the above error. I’m on an Debian unstable system (x86_64), with kernel 5.5.1

As a workaround, I found out (see https://github.com/electron/electron/issues/17972) that

sudo sysctl kernel.unprivileged_userns_clone=1

makes it work again.

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Reactions: 4
  • Comments: 23 (10 by maintainers)

Commits related to this issue

Most upvoted comments

@saghul I can make a PR to add it if interested

We build it already and it seems to work fine: https://github.com/freifunkMUC/jitsi-meet-electron/releases/latest

I vote for debian packages 😃

I think I misread @vladimiry 's comment 🤦 I’ve spent some time trying to get it to work but AFAICT doing the repackage-package dance might be the only way forward, and I have no energy left for that.

At least with the current way it will work for thoe who want to create Debian packages…

Would creating a flatpak help here?

Yes, flatpak always helps. Flatpak runs on all distro’s, has integration for all desktops and the package can be upgraded with software center if published on Flathub.

@saghul we also saw the Problem, that’s why we released the deb so People can start the stuff with --no-sandbox, which helps those people. The problem seems only to exist for Debian Buster and running everywhere without sandbox does not seem a good idea.

Tried to fix it on https://github.com/jitsi/jitsi-meet-electron/pull/235 and made a beta 4, but alas the problem persists 😕