El 22/10/25 a las 22:31, Alan Mackenzie escribió:
Hello, Javier.On Wed, Oct 22, 2025 at 21:59:11 +0200, Javier Martinez wrote: [ .... ]And some good news for you: Someone had to maintain pipewire to allow non pulseaudio users to have sound in firefox thanks to some developers that impose dependencies in one audio system discarding others. And in that question systemd and pulseaudio are very responsible by it's way of doing things.Well, I haven't really paid much attention to such things, but I've got sound in firefox, and both pulseaudio and system-pipewire are disabled. Maybe the firefox build is automatically enabling pulseaudio for me, or something equally wicked.Without all damage done by systemd developers maybe it would be just need to compile firefox to use standard sound system without requiring "a sound daemon".I agree with you. I don't know what a "sound daemon" is; what it does, what it's for. It seems to me to be a redundant daemon adding no functionality. It is more fat (as opposed to muscle) in the system, and must be an extra place where security problems can occur. Up to my newest machine (August 2024), alsa has always worked well for me. But if anybody can explain what a "sound daemon"'s for, what I can do with it that I couldn't do without it, I'm all ears.
One sound daemon was esd for example, was designed to avoid that if you were watching a movie in your computer you couldn't use sound in any other application (as in firefox for example) if get's blocked. So the sound daemon allowed sharing the sound card between all applications. However pulseaudio is not only a sound daemon, is a sound daemon that substitute everything and impose his own way to do things.
You can use firefox without pulseaudio and without pipewire with apulse, so one pulseaudio emulator for alsa, so you need one pulseaudio emulator to be able to play sound in firefox.
OpenPGP_0x57E64E0B7FC3BEDF.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
