[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: Audio output from firefox
On Sun, Mar 19, 2017 at 10:00:09PM -0400, Ian D. Leroux wrote:
> On Sun, Mar 19, 2017, at 21:44, scole_mail wrote:
> > Here are some links claiming firefox is dropping alsa support for linux
> > http://www.omgubuntu.co.uk/2017/03/firefox-52-no-sound-pulseaudio-alsa-linux
> > https://bugzilla.mozilla.org/show_bug.cgi?id=1247056
> > so maybe pulseaudio is the way to go anyway.
> Someone correct me if I'm wrong, but as far as I've been able to
> determine the kerfuffle about firefox requiring pulseaudio is all about
> what is enabled in the stock binaries compiled and distributed by
> mozilla. Since anyone using pkgsrc is (directly or indirectly) using
> binaries that were compiled independently of mozilla, that doesn't have
> any direct impact on us. Of course, that still leaves two issues:
> - what the best default build options for pkgsrc might be (I have no
> opinion, since I compile my own packages anyway and can set non-default
> options if I wish).
> - whether alsa or oss support will bitrot in the long run if the
> community assumes that everyone uses pulseaudio. Presumably that
> depends on those of us who care having enough time and energy to keep
> the non-pulseaudio backends working.
A pulseaudio shim might be the way to go. Pulseaudio and Systemd have
the same daddy. Since FireFox is changing its plugin design aswell, it
might be a better option updating whatever is needed in package source
to supply audio to Webkit Browsers.
Seamonkey is a pretty good fork, I just don't think it has the
reasources to fork that far away from FireFox (no pulseaudio
The hard Rust dependancy in FireFox will be a greater turn of for me.
But it was expected.
> To return to the OP's problem: is the pulseaudio daemon actually
> -- IDL
Main Index |
Thread Index |