Can't use microphone in ungoogled-chromium

DoneSubmitted by Brian Leung.
Details
8 participants
  • Brian Leung
  • Christopher Lemmer Webber
  • Jack Hill
  • Ludovic Courtès
  • Pierre Neidhardt
  • Mathieu Lirzin
  • Marius Bakke
  • Mathieu Lirzin
Owner
unassigned
Severity
normal
B
B
Brian Leung wrote on 7 Aug 2019 18:20
(address . bug-guix@gnu.org)
CAAc=MEweTCNS_B-3yCNzqaKKKgDWuS94vH4DbR1g=SfS4NEp0g@mail.gmail.com
When a microphone is plugged in, ungoogled-chromium fails to detect it.
Attachment: file
M
M
Mathieu Lirzin wrote on 12 Aug 2019 12:38
(name . Brian Leung)(address . bkleung89@gmail.com)(address . 36961@debbugs.gnu.org)
871rxqu0rn.fsf@gnu.org
Brian Leung <bkleung89@gmail.com> writes:
Toggle quote (2 lines)> When a microphone is plugged in, ungoogled-chromium fails to detect it.
I have the same issue here.
-- Mathieu LirzinGPG: F2A3 8D7E EB2B 6640 5761 070D 0ADE E100 9460 4D37
J
J
Jack Hill wrote on 19 Aug 2019 20:43
Can't use microphone in ungoogled-chromium
(address . 36961@debbugs.gnu.org)
alpine.DEB.2.20.1908191439030.9756@marsh.hcoop.net
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
L
L
Ludovic Courtès wrote on 26 Aug 2019 14:36
(name . Mathieu Lirzin)(address . mthl@gnu.org)
87y2zgxfvy.fsf@gnu.org
Hello,
Mathieu Lirzin <mthl@gnu.org> skribis:
Toggle quote (6 lines)> 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 onhttps://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 wrongPulseAudio input by default?
Thanks,Ludo’.
C
C
Christopher Lemmer Webber wrote on 26 Aug 2019 14:56
(address . bug-guix@gnu.org)
87pnksnkz7.fsf@dustycloud.org
Ludovic Courtès writes:
Toggle quote (20 lines)> 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 hadto *both* open pavucontrol and select the right input device and enableit (it was muted) also click on the microphone button (I don't rememberwhere) and select the particular device. Once I did that, worked like acharm.
P
P
Pierre Neidhardt wrote on 27 Aug 2019 17:47
bug#36961: Can't use microphone in ungoogled-chromium
(address . 36961@debbugs.gnu.org)
87ef16sj84.fsf@ambrevar.xyz
I have the same issue, but the pavucontrol trick does not do it for meas I have only one microphone (the one of my webcam on my laptop) andit'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 Neidhardthttps://ambrevar.xyz/
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiEEUPM+LlsMPZAEJKvom9z0l6S7zH8FAl1lUKsACgkQm9z0l6S7zH+rmwf+NS7aghB4zzNzirqI7jdQQig+grdoIIV7RyxcByXLQuIx5FFaU55iD5ShU/bqWbpBeUfqC6qer2G7cwod0NaVJ33VnBUqTrkoisL3I2aUSTctmsiDETNJ6mxlU43Bf4x/JchPrdgrgry6IZuwC096YUKu0rm+ueEY10lXB732Lo6SbrzCfWwEEEJXj2o1lVMreB1lv8qu3IPIhErwttsRG3n3E7ct5twHKqa7TUHY19HG8JVH+v+CVnLGmWtXj+oAuc1QctvAU7t2jYH/Ogq0NcTA8ky0ClNdcC7sMfQQS85X+Y4OMm7xUxQjZPBSf9R1rThN8cQKb8QYEFz3Uidxbg===eDW+-----END PGP SIGNATURE-----
M
M
Mathieu Lirzin wrote on 27 Aug 2019 20:13
(address . 36961@debbugs.gnu.org)
87v9uieasy.fsf@nereide.fr
Pierre Neidhardt <mail@ambrevar.xyz> writes:
Toggle quote (9 lines)> 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 micactivated in pavucontrol.
Attachment: mic-error.png
-- Mathieu LirzinGPG: F2A3 8D7E EB2B 6640 5761 070D 0ADE E100 9460 4D37
L
L
Ludovic Courtès wrote on 27 Aug 2019 23:36
(name . Mathieu Lirzin)(address . mathieu.lirzin@nereide.fr)
87o90amgtv.fsf@gnu.org
Hi Mathieu,
Mathieu Lirzin <mathieu.lirzin@nereide.fr> skribis:
Toggle quote (14 lines)> 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 usethe microphone or webcam, which in turn should trigger a dialog box fromthe browser where you can allow/disallow and choose devices. Did you gothrough that process?
HTH,Ludo’.
P
P
Pierre Neidhardt wrote on 28 Aug 2019 00:07
87d0gquurt.fsf@ambrevar.xyz
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 grantedto meet.jit.si.
The compile-time configuration javascript that Jack mentioned might havesomething to do with this.
-- Pierre Neidhardthttps://ambrevar.xyz/
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiEEUPM+LlsMPZAEJKvom9z0l6S7zH8FAl1lqbYACgkQm9z0l6S7zH8Ihgf/TiczXsSk0UwKh0R3rKSuUDCBO7LKPg0NMp71yU0qBrEH+fdmBFImTVa1kK0YqqDO4kDnE+ZmQM5KlWVb4QSB0AJ0jN0oZhdgnm4tojQMbcrHBUXbi4i43pfdK4ytRIfspebrhRqWIbBM9Otp8Oki07pjW6eJJ/AopTn9F3OH7oVZ1nIZ6gorRtyTS0ShXyoiLg9tfu7BRxit2aiVQZijfcpCTBTvCa+fxVCbyRpCH4m7hSiESm5NyWpXydWV1D1zGjJCIqrEShAUA3SBeLL4qU7B9mJxjf4bO0wcgQk/nS9QlzgYlcuqxkRNlDiEZkQsoRICsGPzwTXDnSADZbQbVQ===54Sa-----END PGP SIGNATURE-----
M
M
Mathieu Lirzin wrote on 3 Sep 2019 13:06
(name . Ludovic Courtès)(address . ludo@gnu.org)
87o9013ah5.fsf@nereide.fr
Hello Ludo,
Ludovic Courtès <ludo@gnu.org> writes:
Toggle quote (23 lines)> 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 Jitsibut Chromium fallback to "blocked" even when manually selecting the"allowed" (either in the URL bar icon or in chromium settingsinterface).
-- Mathieu LirzinGPG: F2A3 8D7E EB2B 6640 5761 070D 0ADE E100 9460 4D37
M
M
Marius Bakke wrote on 4 Sep 2019 13:19
87lfv4gvge.fsf@devup.no
Pierre Neidhardt <mail@ambrevar.xyz> writes:
Toggle quote (7 lines)> 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 frommaster_preferences.json solves this issue. Fix pushed in5ee1c0459eebdd3b7771abaeab0f0b52ff86fdd5.
For existing Chromium profiles, you will need to close all browserwindows and run
sed -i 's/"audio_capture_enabled":false/"audio_capture_enabled":true/' \ ~/.config/chromium/Default/Preferences
...to get the new default.
Thanks!
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAl1vncEACgkQoqBt8qM6VPpe4wf+MCbwSA/17VSQoCb5wUKyAJTV74vcItHMURjsqNmNiHx3FWzkgLUnYJXgRiEqxRX6LVkFJpdV7e+9vrH8GGQhhZbaeGc2gWgIxQR8PlitwBFgASFNuP2YhqcA+YnFpYi3zvIV72ekpVDy5qRYDSIjfzKuiBEmFNKf6mslPtm62vkW+X1G9QhhxVzk1EultM/nWAXRojgXHJYEBB3MAGe8ofd1G8noqBPLGJyWGgHr1fjlgsWRNe2EhFXCgk2RRr1XoYDFL1aVXSW7Qec5XKuoMBeuD4c1sb+spZDgwIprEQYdoAFZvw50TNqoM5MbzJOXcHmFX5uXuhjPa8PfMmvGRg===dp33-----END PGP SIGNATURE-----
Closed
M
M
Mathieu Lirzin wrote on 4 Sep 2019 13:39
(name . Marius Bakke)(address . mbakke@fastmail.com)
87woeo1e9z.fsf@nereide.fr
Hello Marius,
Marius Bakke <mbakke@fastmail.com> writes:
Toggle quote (25 lines)> 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 LirzinGPG: F2A3 8D7E EB2B 6640 5761 070D 0ADE E100 9460 4D37
Closed
B
B
Brian Leung wrote on 4 Sep 2019 21:39
(name . Mathieu Lirzin)(address . mthl@gnu.org)
CAAc=MEymX7GxUC=YD63DT37SV7ETzfQCt4TK5W82P7VA_aThPw@mail.gmail.com
Hi Marius,
I'm getting a build error with the latest push. I've attached the log;anyone else have the same issue?
Thanks,Brian
On Wed, Sep 4, 2019 at 1:39 PM Mathieu Lirzin <mthl@gnu.org> wrote:
Toggle quote (35 lines)> 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>
Attachment: file
Closed
?
Your comment

This issue is archived.

To comment on this conversation send email to 36961@debbugs.gnu.org