GNU bug report logs - #36961
Can't use microphone in ungoogled-chromium

Previous Next

Full log

Message #17 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Christopher Lemmer Webber <cwebber <at> dustycloud.org>
To: bug-guix <at> gnu.org
Cc: 36961 <at> debbugs.gnu.org, Brian Leung <bkleung89 <at> gmail.com>,
 Mathieu Lirzin <mthl <at> gnu.org>
Subject: Re: bug#36961: Can't use microphone in ungoogled-chromium
Date: Mon, 26 Aug 2019 08:56:44 -0400

Ludovic Courtès writes:

> Hello,
>
> Mathieu Lirzin <mthl <at> gnu.org> skribis:
>
>> Brian Leung <bkleung89 <at> 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.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.