Hello, Mathieu Lirzin <m...@gnu.org> skribis:
> Brian Leung <bkleun...@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’.
