When I try to launch the omniverse-launcher-linux.AppImage
on CentOS 7.9 [Mate], I get the following:
[24014:0817/143224.344030: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_omnivei0eNv2/chrome-sandbox is owned by root and has mode 4755.
Trace/breakpoint trap (core dumped)
Hello @awilliams2! This looks like an issue with Linux Sandboxing. According to their documentation, this issue can happen with any program build on the top of an Electron Framework. I did a search and found 3 possible solutions that you can try.
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 (Probably the 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
Let me know if any of these has helped!
Hi Wendy,
Thanks for all the info. Running with --no-sandbox
seems to have solved the issue for us.
Cheers