bug#36961: Can't use microphone in ungoogled-chromium

bug#36961: Can't use microphone in ungoogled-chromium

[Brian Leung]

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

When a microphone is plugged in, ungoogled-chromium fails to detect it.

[-- Attachment #2: Type: text/html, Size: 97 bytes --]

bug#36961: Can't use microphone in ungoogled-chromium

[Mathieu Lirzin]

Brian Leung <bkleung89@gmail.com> writes:

> When a microphone is plugged in, ungoogled-chromium fails to detect it.

I have the same issue here.

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

bug#36961: Can't use microphone in ungoogled-chromium

[Jack Hill]

I think that this is related to the same thing that is being discussed in 
upstream issue 785 
<https://github.com/Eloston/ungoogled-chromium/issues/785>. In particular, 
it looks like Guix is disabling audio capture ins master-preferences.json 
<https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/aux-files/chromium/master-preferences.json#n21>.

I haven't yet had a chance to dig deeper or try a fix, apologies.

I'm also curious to know why it was disabled before recommending that it 
be changed.

All the best,
Jack

bug#36961: Can't use microphone in ungoogled-chromium

[Ludovic Courtès]

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

bug#36961: Can't use microphone in ungoogled-chromium

[Christopher Lemmer Webber]

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.

bug#36961: Can't use microphone in ungoogled-chromium

[Pierre Neidhardt]

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

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

-- 
Pierre Neidhardt
https://ambrevar.xyz/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

bug#36961: Can't use microphone in ungoogled-chromium

[Mathieu Lirzin]

[-- 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

bug#36961: Can't use microphone in ungoogled-chromium

[Ludovic Courtès]

Hi Mathieu,

Mathieu Lirzin <mathieu.lirzin@nereide.fr> skribis:

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

That’s about granting permission to use the microphone.

Jitsi should have a button to request permission for the web page to use
the microphone or webcam, which in turn should trigger a dialog box from
the browser where you can allow/disallow and choose devices.  Did you go
through that process?

HTH,
Ludo’.

bug#36961: Can't use microphone in ungoogled-chromium

[Pierre Neidhardt]

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

In Chromium if you click on the camera button right of the address bar,
you can see the per-domain permissions.  In my case, they are granted
to meet.jit.si.

The compile-time configuration javascript that Jack mentioned might have
something to do with this.

-- 
Pierre Neidhardt
https://ambrevar.xyz/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

bug#36961: Can't use microphone in ungoogled-chromium

[Mathieu Lirzin]

Hello Ludo,

Ludovic Courtès <ludo@gnu.org> writes:

> Mathieu Lirzin <mathieu.lirzin@nereide.fr> skribis:
>
>> 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.
>
> That’s about granting permission to use the microphone.
>
> Jitsi should have a button to request permission for the web page to use
> the microphone or webcam, which in turn should trigger a dialog box from
> the browser where you can allow/disallow and choose devices.  Did you go
> through that process?

Yes, I have tried to manually force allowing of the microphone for Jitsi
but Chromium fallback to "blocked" even when manually selecting the
"allowed" (either in the URL bar icon or in chromium settings
interface).

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

bug#36961: Can't use microphone in ungoogled-chromium

[Marius Bakke]

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

Pierre Neidhardt <mail@ambrevar.xyz> writes:

> In Chromium if you click on the camera button right of the address bar,
> you can see the per-domain permissions.  In my case, they are granted
> to meet.jit.si.
>
> The compile-time configuration javascript that Jack mentioned might have
> something to do with this.

Hello!

Sorry for the slow response here...

I can confirm that removing audio_capture_enabled from
master_preferences.json solves this issue.  Fix pushed in
5ee1c0459eebdd3b7771abaeab0f0b52ff86fdd5.

For existing Chromium profiles, you will need to close all browser
windows and run

 sed -i 's/"audio_capture_enabled":false/"audio_capture_enabled":true/' \
     ~/.config/chromium/Default/Preferences 

...to get the new default.

Thanks!

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

bug#36961: Can't use microphone in ungoogled-chromium

[Mathieu Lirzin]

Hello Marius,

Marius Bakke <mbakke@fastmail.com> writes:

> Pierre Neidhardt <mail@ambrevar.xyz> writes:
>
>> In Chromium if you click on the camera button right of the address bar,
>> you can see the per-domain permissions.  In my case, they are granted
>> to meet.jit.si.
>>
>> The compile-time configuration javascript that Jack mentioned might have
>> something to do with this.
>
> Hello!
>
> Sorry for the slow response here...
>
> I can confirm that removing audio_capture_enabled from
> master_preferences.json solves this issue.  Fix pushed in
> 5ee1c0459eebdd3b7771abaeab0f0b52ff86fdd5.
>
> For existing Chromium profiles, you will need to close all browser
> windows and run
>
>  sed -i 's/"audio_capture_enabled":false/"audio_capture_enabled":true/' \
>      ~/.config/chromium/Default/Preferences 
>
> ...to get the new default.

This fix worked for me, thank you very much!

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