all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mathieu Lirzin <mathieu.lirzin@nereide.fr>
To: 36961@debbugs.gnu.org
Cc: bkleung89@gmail.com, Pierre Neidhardt <mail@ambrevar.xyz>
Subject: bug#36961: Can't use microphone in ungoogled-chromium
Date: Tue, 27 Aug 2019 20:13:33 +0200	[thread overview]
Message-ID: <87v9uieasy.fsf@nereide.fr> (raw)
In-Reply-To: <87ef16sj84.fsf@ambrevar.xyz> (Pierre Neidhardt's message of "Tue, 27 Aug 2019 17:47:55 +0200")

[-- Attachment #1: Type: text/plain, Size: 495 bytes --]

Pierre Neidhardt <mail@ambrevar.xyz> writes:

> I have the same issue, but the pavucontrol trick does not do it for me
> as I have only one microphone (the one of my webcam on my laptop) and
> it's not muted.
>
> ungoogled-chromium complains about an "Error obtaining microphone permission."
>
> Note that both the webcam and the microphone work in other contexts
> (e.g. audacity, appear.in).

Here is a screenshot of the error message I get in chromium with the mic
activated in pavucontrol.


[-- Attachment #2: chromium mic error --]
[-- Type: image/png, Size: 82360 bytes --]

[-- Attachment #3: Type: text/plain, Size: 76 bytes --]


-- 
Mathieu Lirzin
GPG: F2A3 8D7E EB2B 6640 5761  070D 0ADE E100 9460 4D37

  reply	other threads:[~2019-08-27 18:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-07 16:20 bug#36961: Can't use microphone in ungoogled-chromium Brian Leung
2019-08-12 10:38 ` Mathieu Lirzin
2019-08-26 12:36   ` Ludovic Courtès
2019-08-26 12:56     ` Christopher Lemmer Webber
2019-08-19 18:43 ` Jack Hill
2019-08-27 15:47 ` Pierre Neidhardt
2019-08-27 18:13   ` Mathieu Lirzin [this message]
2019-08-27 21:36     ` Ludovic Courtès
2019-08-27 22:07       ` Pierre Neidhardt
2019-09-04 11:19         ` Marius Bakke
2019-09-04 11:39           ` Mathieu Lirzin
2019-09-03 11:06       ` Mathieu Lirzin

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=87v9uieasy.fsf@nereide.fr \
    --to=mathieu.lirzin@nereide.fr \
    --cc=36961@debbugs.gnu.org \
    --cc=bkleung89@gmail.com \
    --cc=mail@ambrevar.xyz \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.