Solve “The SUID sandbox helper binary was found, but is not configured correctly.” (3 solutions!)

Authmane Terki
1 min readMay 2, 2020

--

Hello,

Today I downloaded and tried to run Lossless-cut on Debian 10 Buster system, and I got this error:

$ ./LosslessCut-linux.AppImage
[479026:0502/185909.649080: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_lossle3kkVRT/chrome-sandbox is owned by root and has mode 4755.
fish: “lossless-cut” terminated by signal SIGTRAP (Trace or breakpoint trap)

So I tried again with the .tar.bz2 Losslesscut archive rather than the .AppImage file. But again:

$ ./LosslessCut-linux/losslesscut
[471021:0502/185447.408238: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 /home/authmane512/Downloads/LosslessCut-linux/chrome-sandbox is owned by root and has mode 4755.
fish: “./Downloads/LosslessCut-linux/l…” terminated by signal SIGTRAP (Trace or breakpoint trap)

This problem happens with every program that is built on the top of Electron framework.

Solution #1

If the program is not packaged in a .AppImage file, you can simply set the right permissions to the chrome-sandbox file:

cd LosslessCut-linux
sudo chown root:root chrome-sandbox
sudo chmod 4755 chrome-sandbox

Solution #2 (easiest one)

You can run the app with the --no-sandbox argument:

./LosslessCut-linux.AppImage --no-sandbox

Solution #3

Enable unprivileged access to CLONE_NEWUSER in your kernel:

sysctl kernel.unprivileged_userns_clone=1

I don’t what is unprivileged access, if you know leave a comment 😉!

--

--