-
Notifications
You must be signed in to change notification settings - Fork 588
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chromium: no sound with pipewire #4855
Comments
If no one else has an idea, I would suggest to narrow it down with something like |
@rusty-snake That was a very good idea, thanks. |
The follow-up from Mad Horse on the original bug has a hint:
No idea what the new version of chromium means by "secure directory", but I added |
The directory will have to be hardcoded and activated by default by --private and --whitelist commands. For example we have alsa and pulse brought in by default by --private:
Do we know what directories (runtime and config under /home/username) are they using? My impression is pipewire is still under heavy development. I'm not sure what's happening in Fedora, probably this is where it will be deployed first. Anyway, I'm going for a test release (0.9.68~rc1) next week, the big release two weeks later. We can wait to bring in pipewire if needed. |
Pipewire works actually fine. It's already whitelisted in includes:
The problem I had was just very specific to my setup, as I have manually pointed the runtime path to somewhere else. |
OK, thanks! If they come with a user file or directory under /home/username we'll make it default later. |
FWIW
These are the deamon config files, there is |
I'll make it default as ~/.config/pipewire/pipewire.conf |
This file is read by pipewire (the deamon). IDK if the client library read's it too but I don't think so. If we allow it inside the sandbox, it must be read-only (it's turing complete and pipewire isn't sandboxed). |
OK, so we don't need to add it for --private/--whitelist. Question: is --nosound option working on a pipewire setup? |
Just tested it. Edit: but as mentioned, I have my pipewire rundir (which has the socket) in a non-standard path. |
--nosound should be fine now if XDG_RUNTIME_DIR env variable is configured or if the socket is under /run/user/UID/pipewire-* |
I think this one is closed. |
Someone on the Debian bug tracker reported that Chromium 97 no longer plays sound when firejailed.
I was able to reproduce that.
I narrowed it down to whitelists inside the HOME directory.
I.e. I disabled
include whitelist-common.inc
and allwhitelist ${HOME}/...
in chromium.profile and chromium-common.profile, and then sound was working again.But I have problems figuring out which additional directory needs to be whitelisted.
I tried
--trace
(which just hangs and doesn't even open the Chromium window),--trace=file
(which opens the windows, but does not load a website) and then usedstrace
to log opened files.But nothing looks sound-related in there.
Here is the console output with broken sound:
The text was updated successfully, but these errors were encountered: