[linux] chrome-sandbox problems

[jamshark70]

$ ./OSC-for-OBS

[89410:0624/141818.915489: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 /home/dlm/share/debs/OSC-for-OBS-v3.1.3-Linux/chrome-sandbox is owned by root and has mode 4755.
Trace/breakpoint trap (core dumped)

OK... chmod 4755 chrome-sandbox and sudo chown root chrome-sandbox:

$ ls -l chrome-sandbox
-rwxr-xr-x 1 root dlm 4746192 Dec  6  2022 chrome-sandbox

$ ./OSC-for-OBS

[89410:0624/141818.915489: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 /home/dlm/share/debs/OSC-for-OBS-v3.1.3-Linux/chrome-sandbox is owned by root and has mode 4755.
Trace/breakpoint trap (core dumped)

$ sudo ./OSC-for-OBS 
[sudo] password for dlm: 
[89435:0624/141951.794702:FATAL:electron_main_delegate.cc(253)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180.
Trace/breakpoint trap

After that, I get valid behavior by running ./OSC-for-OBS --no-sandbox (either sudo or not, not running as root does pop stuff up in Chrome for no clear reason).

I've got it running, and successfully /setRecording-ed 👍 so this isn't urgent, but from a UX perspective, users may expect to be able to open the application and get an interface window. In reality, it's necessary to discover an undocumented command line option.

[jshea2]

Oh interesting, thanks for the heads-up and finding a workaround! I don’t have a Linux machine to test on, so I’ve just been packaging the Linux build from my Mac. I'll try and troubleshoot it if i get a RPi 👍