Follow the same audio sandboxing policy as Google Chrome, off experimantal feature that causes problems

This commit is contained in:
Mikhail Novosyolov 2021-03-14 19:02:05 +03:00
parent 023d679d21
commit 703a7ad6bf

View file

@ -120,6 +120,10 @@ if [ $want_debug -eq 1 ] ; then
$GDB "$LIBDIR/$APPNAME" -x $tmpfile
exit $?
else
exec $LIBDIR/$APPNAME $SANDBOX ${CHROMIUM_FLAGS} "--password-store=basic" "$@"
# --disable-features=AudioServiceSandbox makes Chromium use the same policy as Chrome and fixes issues with
# accessing /run/user/%d/pulse/* on rosa2019.1+
# services/audio/audio_sandbox_hook_linux.cc in general looks like hackery with hardcoded paths
# https://bugs.chromium.org/p/chromium/issues/detail?id=1018580
exec $LIBDIR/$APPNAME $SANDBOX ${CHROMIUM_FLAGS} "--password-store=basic" "--disable-features=AudioServiceSandbox" "$@"
fi