On 2/19/22 05:53, Francesco Poli wrote:
On Thu, 10 Feb 2022 20:51:43 +0100 Francesco Poli wrote:
On Mon, 7 Feb 2022 03:48:15 -0500 Andres Salomon wrote:
[...]
Edit /etc/chromium.d/default-flags, and add
--disable-features=AudioServiceSandbox to one of those CHROMIUM_FLAGS
variables. That should get you set as a workaround for this bug.
OK, so I upgraded to chromium/98.0.4758.80-1 and added the following
lines at the end of '/etc/chromium.d/default-flags':
# Disable audio service sandbox (bug #1003622)
export CHROMIUM_FLAGS="$CHROMIUM_FLAGS
--disable-features=AudioServiceSandbox"
This works around the bug and makes the microphone work on
<https://www.onlinemictest.com/>, on<https://meet.jit.si>, and on
<https://meet.google.com>
I'm enabling pipewire in the 98.0.4758.80-2 build, which I plan to
upload in a few days - please give that a try once it's uploaded to see
if that helps with this bug.
Please let me know, when I should try and disable the workaround, in
order to check whether the bug is actually fixed.
I have just upgraded to chromium/98.0.4758.102-1 and tested it.
Without the above-described workaround, the microphone still fails to
work on<https://www.onlinemictest.com/> (same permission error).
With the workaround, the microphone works.
Hence, I would say that this new version of the chromium package does
not make any difference with respect to the microphone bug.
Please let me know, when there's any news on this bug.
Thanks for your time!
So according to upstream (btw the link points to the wrong place in the
file, just search the file for the string 'AudioService'):
"Audio process sandbox is disabled in official builds, but enabled on
ToT via a field trial
https://source.chromium.org/chromium/chromium/src/+/main:testing/variations/fieldtrial_testing_config.json;l=857?q=AudioServiceSandbox&ss=chromium%2Fchromium%2Fsrc&start=11
<https://source.chromium.org/chromium/chromium/src/+/main:testing/variations/fieldtrial_testing_config.json;l=857?q=AudioServiceSandbox&ss=chromium%2Fchromium%2Fsrc&start=11>."
That's why it works for you with the official binary, but not in Debian.
We have "fieldtrial_testing_like_official_build=true" set during our
build, but chromium spits out a warning saying it's unknown. I suspect
what happened was that upstream renamed it to
"disable_fieldtrial_testing_config", and that we need to be setting that
to true, but I haven't tested that theory yet. I need to do some other
stuff first for v98 in unstable/bullseye, and then I'll either prepare a
v100 build in experimental with that option set, or (after further
research to see what it changes) try it in a v98 sid build.
