7e6d6e034d
Just silencing the error will not prevent Chromium from trying to start
up the SUID sandbox anyway, thus flooding stderr with:
LaunchProcess: failed to execvp:
After digging a bit in the source code I found out that the SUID sandbox
binary is indeed used, but only for setting oom_score_adj within the
user namespace (as "root"). So let's build the sandbox binary and of
course don't set setuid bit.
These annoying error messages were originally introduced by
|
||
---|---|---|
.. | ||
source | ||
browser.nix | ||
common.nix | ||
default.nix | ||
plugins.nix | ||
update.sh |