Hi Mad Horse, On Thu, Jan 13, 2022 at 05:07:38PM +0800, Mad Horse wrote: > After upgraded to 97.0.4692.71-0.1, Chromium running inside firejail can no > longer play sound (e.g. when playing an online video), while bare Chromium > can. It is shown with PulseAudio Manager that the Chromium running inside > firejail cannot connect to the sound server while the bare Chromium can.
I had a similar issue initially as well. But it turned out to be related
to my custom sound setup (using pipewire with run directory in ~/pipewire).
There are also no sound-related Chromium issue known in the upstream
firejail bug tracker.
So I think it also has to be related to your setup.
It might be related to some whitelist in the chromium{-common}.profile,
as this causes the parent directory to get blocked.
Can you please try to figure out which path needs to be whitelisted
on your system to get it working again?
Kind regards,
Reiner
signature.asc
Description: PGP signature
