Is "media.cubeb.backend = oss" set in firefox?
Thanks. I still do not understand.You type media.cubeb.backend in the url and press + button and string and set it the value to the soundserver you use.
you don't put that in the address bar - you should add it to the configuration firefox hides under "about:config".I put "media.cubeb.backend+" in the URL bar, and then? What do you mean with "string"?
...and annoying everyone with default settings and features nobody needs or asked for... (e.g. leaking IPs and local hostnames to search engines)Firefox guys love pulse.
PulseAudio is a sound server, basically an optional intermediate layer between the OSS sound system (or ALSA on Linux) and applications. It was primarily designed to work around the limitations of ALSA, and is not very useful on FreeBSD because OSS is more powerful than ALSA and has most of the features PulseAudio offers built in. In some cases you have to run it because it's the only audio backend supported by a few programs, but otherwise it's a wise idea not to add useless complexity and therefore to avoid running PulseAudio when it's not necessary.And I have no idea what is pulseaudio and what pooled it in as dependency.
media.cubeb.backend
is manually set, Firefox will automatically choose the backend it considers the most relevant. Besides OSS, ALSA and PulseAudio, it can also output sound to JACK and sndio. If PulseAudio is running, it will use it as a primary choice over OSS, therefore if PA's output is muted, or is set to a wrong channel/device, you'll get no sound although another program using OSS directly will play fine. You solved it by telling Firefox to use OSS although PA is running, but stopping PA or setting it up properly would have worked the same way, so black magic in about:config is not an absolute must in this context (but a good idea anyway) If PulseAudio is running, it will use it as a primary choice over OSS,
ps ax | grep pulse
942 - S 0:14.08 /usr/local/bin/pulseaudio --start --log-target=syslog
1132 1 S+ 0:00.00 grep pulse
twm
.% pkg info -rx pulseaudio
pulseaudio-14.2:
speech-dispatcher-0.10.2
% pkg info -rx speech-disp
speech-dispatcher-0.10.2:
chromium-91.0.4472.114_1
IIRC you have to create it the way Alain De Vos already explained.
To prevent pulseaudio from actually being started if something (unnecessarily) pulls it as a dependency, I usually just (re)move the binary from /usr/local/bin and 'ln -s /bin/true /usr/local/bin/pulseaudio'.
Always work with the system and not against.
autospawn=yes
This does not anwser my above question: why the hell it is being started?Then relog or restart and pulseaudio should now no longer appear.
This does not anwser my above question: why the hell it is being started?
ProbablyCase 2: One of your programs that you use, is compiled with pulseaudio support and starts pulseaudio automatically too.
firefox
is doing it, although it is configured as recommended above for not using it.sko said:i.e. renaming or removing the /usr/local/bin/pulseaudio binary.
pkg delete -f pulseaudio
. After that, look for applications that do not work correctly or seem to hang sometimes. These likely were the applications that started it. If you install using packages, try to solve it with the app's config file. If that won't work you might consider a reinstall from ports where you disabled pulseaudio with make config
.Just see, what I wrote above:pkg info -r pulseaudio
should show the packages on your system which require pulseaudio.
OPTIONS_UNSET+=PULSE
OPTIONS_UNSET+=PULSEAUDIO
OPTIONS_SET+=SNDIO
It won't matter whether or not you start chromium -- pulseaudio was installed as a software dependency, just because chromium was installed.Just see, what I wrote above:
(1) I did pkg info -r, pulseaudio is demanded by speech-dispatcher-0.10.2 and chromium-91.0.4472.114_1
(2) I did not start chromium, also not speech-dispatcher (not even know what that is).
Hence, something else, just because it was compiled with pulseaudio, just because pulseaudio was
downloaded, is starting pulseaudio. Logic?
I find this behaviour awful.
Next boot I will do "ps -ax" immediately before and immediately after starting firefox.
pkg info -r
can also be used to find the requirements of chromium and speech-dispatcher, and so on, all the way up the software dependency chain.It won't matter whether or not you start chromium -- pulseaudio was installed as a software dependency, just because chromium was installed.pkg info -r
can also be used to find the requirements of chromium and speech-dispatcher, and so on, all the way up the software dependency chain.