From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Firefox no sound without PulseAudio
Date: Tue, 19 Jul 2022 23:17:27 +0200 [thread overview]
Message-ID: <20220719211727.-gr-ExvBLV3bd9dpPcgyC27YVmMU4Z3GPRRoWUZw0QA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34596@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 968 bytes --]
New comment by Duncaen on void-packages repository
https://github.com/void-linux/void-packages/issues/34596#issuecomment-1189559492
Comment:
https://bugzilla.mozilla.org/show_bug.cgi?id=1345661
Audio in firefox is a little more complicated than just the cubeb backend due to sandboxing and having separate content processes. Mozilla disabled alsa support a long time ago and basically said that they don't support it any further, there are still people who afterwards contributed patches to make it work and they landed upstream. But I fully understand why they don't support it, the alsa user experience and the api in general is simply not user friendly and doesn't work out of the box for most users.
I would suggest you to use a sound server, like pulse or pipewire, if you still want to use alsa for some reason, look up how to debug libcubeb and how to debug sandbox issues in firefox, both have their own environment variables for more verbose logging.
next prev parent reply other threads:[~2022-07-19 21:17 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 22:26 [ISSUE] " notramo
2021-12-18 14:53 ` mvf
2021-12-20 10:50 ` biopsin
2021-12-20 10:52 ` biopsin
2021-12-20 10:52 ` biopsin
2022-01-23 10:52 ` ErinVoid
2022-01-24 18:38 ` [ISSUE] [CLOSED] " paper42
2022-01-24 18:38 ` paper42
2022-07-15 9:22 ` notramo
2022-07-15 9:23 ` notramo
2022-07-15 9:25 ` notramo
2022-07-15 9:33 ` notramo
2022-07-15 9:34 ` notramo
2022-07-15 16:54 ` mvf
2022-07-15 18:15 ` Duncaen
2022-07-19 20:57 ` notramo
2022-07-19 20:57 ` notramo
2022-07-19 21:17 ` Duncaen
2022-07-19 21:17 ` Duncaen [this message]
2022-07-19 21:19 ` Duncaen
2022-07-19 21:21 ` Duncaen
2022-07-19 21:22 ` [ISSUE] [CLOSED] " Duncaen
2022-08-21 18:53 ` notramo
2022-08-21 19:09 ` Duncaen
2022-08-21 19:09 ` Duncaen
2022-08-21 19:10 ` Duncaen
2022-08-21 19:40 ` notramo
2022-08-21 20:07 ` Duncaen
2022-08-21 20:07 ` Duncaen
2022-08-21 20:27 ` notramo
2022-08-21 20:28 ` notramo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220719211727.-gr-ExvBLV3bd9dpPcgyC27YVmMU4Z3GPRRoWUZw0QA@z \
--to=duncaen@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).