From: Marius Bakke <mbakke@fastmail.com>
To: Vagrant Cascadian <vagrant@debian.org>,
Marco van Hulten <marco@hulten.org>
Cc: help-guix@gnu.org
Subject: Re: ungoogled-chromium
Date: Sun, 22 Mar 2020 15:16:46 +0100 [thread overview]
Message-ID: <87imiw4gq9.fsf@devup.no> (raw)
In-Reply-To: <87v9mwlefs.fsf@ponder>
[-- Attachment #1: Type: text/plain, Size: 610 bytes --]
Vagrant Cascadian <vagrant@debian.org> writes:
> I'm curious if you can get audio or microphone access using
> ungoogled-chromium on meet.jit.si... video worked fine for me, but
> neither audio output nor microphone input worked. Are there optional
> plugins needed to make audio work with ungoogled-chromium?
Early revisions of ungoogled-chromium had a bug where websites were
prevented from accessing your microphone.
Check if ~/.config/chromium/Default/Preferences has an entry like
"audio_capture_enabled": false
Removing or inverting that setting should fix the problem in that case.
HTH,
Marius
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-03-22 14:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-22 12:02 ungoogled-chromium Marco van Hulten
2020-03-22 12:17 ` ungoogled-chromium suggests extension Marco van Hulten
2020-03-22 12:31 ` ungoogled-chromium Marius Bakke
2020-03-22 12:37 ` ungoogled-chromium Ricardo Wurmus
2020-03-22 12:58 ` ungoogled-chromium Marco van Hulten
2020-03-22 13:14 ` ungoogled-chromium Vagrant Cascadian
2020-03-22 14:16 ` Marius Bakke [this message]
2020-03-22 16:18 ` ungoogled-chromium Marco van Hulten
-- strict thread matches above, loose matches on Subject: below --
2019-04-19 22:19 ungoogled-chromium Mason Hock
2019-04-20 0:54 ` ungoogled-chromium beoram
2019-04-20 7:27 ` ungoogled-chromium Ricardo Wurmus
2019-04-20 18:12 ` ungoogled-chromium Mason Hock
2019-04-20 19:59 ` ungoogled-chromium Julien Lepiller
2019-04-20 20:10 ` ungoogled-chromium Mason Hock
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87imiw4gq9.fsf@devup.no \
--to=mbakke@fastmail.com \
--cc=help-guix@gnu.org \
--cc=marco@hulten.org \
--cc=vagrant@debian.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 read-only IMAP folder(s) and NNTP newsgroup(s).