unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Lemmer Webber <cwebber@dustycloud.org>
To: 36961@debbugs.gnu.org
Cc: bkleung89@gmail.com, mthl@gnu.org
Subject: bug#36961: Can't use microphone in ungoogled-chromium
Date: Mon, 26 Aug 2019 08:56:44 -0400	[thread overview]
Message-ID: <87pnksnkz7.fsf@dustycloud.org> (raw)
In-Reply-To: <87y2zgxfvy.fsf@gnu.org>

Ludovic Courtès writes:

> Hello,
>
> Mathieu Lirzin <mthl@gnu.org> skribis:
>
>> Brian Leung <bkleung89@gmail.com> writes:
>>
>>> When a microphone is plugged in, ungoogled-chromium fails to detect it.
>>
>> I have the same issue here.
>
> I initially had the same problem (specifically with Jitsi on
> https://riot.im) but switching the input to the right microphone in
> ‘pavucontrol’ fixed it.
>
> So perhaps it’s just that, for some reason, Chromium picks the wrong
> PulseAudio input by default?
>
> Thanks,
> Ludo’.

FWIW I just did a VoIP call using ungoogled-chromium last Friday.  I had
to *both* open pavucontrol and select the right input device and enable
it (it was muted) also click on the microphone button (I don't remember
where) and select the particular device.  Once I did that, worked like a
charm.

  reply	other threads:[~2019-08-26 12:57 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 [this message]
2019-08-19 18:43 ` Jack Hill
2019-08-27 15:47 ` Pierre Neidhardt
2019-08-27 18:13   ` Mathieu Lirzin
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

  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=87pnksnkz7.fsf@dustycloud.org \
    --to=cwebber@dustycloud.org \
    --cc=36961@debbugs.gnu.org \
    --cc=bkleung89@gmail.com \
    --cc=mthl@gnu.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.
Code repositories for project(s) associated with this public inbox

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

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).