On Wed, Jan 17, 2018 at 10:28:46PM +0000, Ken Moffat wrote:
> > > On Tue, Jan 16, 2018 at 01:07:07AM +0100, Tim Tassonis wrote:
> > > > Hi All
> > > >
> > > > On 01/16/2018 12:29 AM, Tim Tassonis wrote:
> [...]
> > > > >
> > > > > A solution on the faulty machine is to start firefox, go to
> > > > > about:config, and then set the property
> > > > >
> > > > > security.sandbox.content.level
> > > > >
> > > > > to 0, instead of 3.
> > > >
> > > > I found a nice explanation for the problem at:
> > > >
> > > > https://github.com/i-rinat/apulse
> > > >
> > > >
> > > > To leave sandboxing active and get alsa sound running, you can also set
> > > >
> > > > security.sandbox.content.syscall_whitelist
> > > >
> > > > to 16, which is the iotcl syscall needed by alsa. For 32bit
> > > > architectures,
> > > > the value is 54.
I've now built b16 with alsa on a second machine: initially no
sound, but setting security.sandbox.content.syscall_whitelist to 16
in about:config, and restarting direfox, fixed it.
Maybe I've left it set like that on the other machine.
ĸen
--
Truth, in front of her huge walk-in wardrobe, selected black leather
boots with stiletto heels for such a barefaced truth.
- Unseen Academicals
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
