Your message dated Wed, 15 Mar 2023 16:41:51 -0400
with message-id <[email protected]>
and subject line Re: chromium: can't access mic ( no audio input ), works fine 
in firefox
has caused the Debian Bug report #934025,
regarding chromium: can't access mic ( no audio input ), works fine in firefox
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
934025: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934025
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: chromium
Version: 76.0.3809.87-2+b1
Severity: important

Dear Maintainer,

Chromium can't access the microphone, the result is the same from multiple 
websites
(meet.jit.si, appear.in, google meet, etc)

When visiting https://webrtc.github.io/samples/src/content/getusermedia/volume/
the console says:

navigator.MediaDevices.getUserMedia error:  Requested device not found 
NotFoundError

Note that this bug is separate from #923028, I do not see any console messages 
about
"not allowed to start", the audio device(s) themselves are invisible to 
chromium.

I have looked in the following files:

/etc/chromium/master_preferences
/usr/share/chromium/master_preferences
~/.config/chromium/Default/Preferences

and there is no key "audio_capture_enabled" anywhere. So the issue seems 
distinct
from #885155 #884887 #889067 as well.

X


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable'), (300, 'unstable'), (200, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages chromium depends on:
ii  chromium-common      76.0.3809.87-2+b1
ii  libasound2           1.1.8-1
ii  libatk-bridge2.0-0   2.30.0-5
ii  libatk1.0-0          2.30.0-2
ii  libatomic1           9.1.0-10
ii  libatspi2.0-0        2.30.0-7
ii  libavcodec58         7:4.1.4-1
ii  libavformat58        7:4.1.4-1
ii  libavutil56          7:4.1.4-1
ii  libc6                2.28-10
ii  libcairo-gobject2    1.16.0-4
ii  libcairo2            1.16.0-4
ii  libcups2             2.2.10-6
ii  libdbus-1-3          1.12.16-1
ii  libdrm2              2.4.97-1
ii  libevent-2.1-6       2.1.8-stable-4
ii  libexpat1            2.2.7-1
ii  libflac8             1.3.2-3
ii  libfontconfig1       2.13.1-2
ii  libfreetype6         2.9.1-4
ii  libgcc1              1:9.1.0-10
ii  libgdk-pixbuf2.0-0   2.38.1+dfsg-1
ii  libglib2.0-0         2.60.6-1
ii  libgtk-3-0           3.24.10-1
ii  libharfbuzz0b        2.5.3-1
ii  libicu63             63.2-2
ii  libjpeg62-turbo      1:1.5.2-2+b1
ii  libjsoncpp1          1.7.4-3
ii  liblcms2-2           2.9-3
ii  libminizip1          1.1-8+b1
ii  libnspr4             2:4.21-1
ii  libnss3              2:3.45-1
ii  libopenjp2-7         2.3.0-2
ii  libopus0             1.3-1
ii  libpango-1.0-0       1.42.4-6
ii  libpangocairo-1.0-0  1.42.4-6
ii  libpci3              1:3.6.2-2
ii  libpng16-16          1.6.37-1
ii  libpulse0            12.2-4
ii  libre2-5             20190101+dfsg-2+b1
ii  libsnappy1v5         1.1.7-1
ii  libstdc++6           9.1.0-10
ii  libvpx6              1.8.1-2
ii  libwebp6             0.6.1-2
ii  libwebpdemux2        0.6.1-2
ii  libwebpmux3          0.6.1-2
ii  libx11-6             2:1.6.7-1
ii  libx11-xcb1          2:1.6.7-1
ii  libxcb1              1.13.1-2
ii  libxcomposite1       1:0.4.4-2
ii  libxcursor1          1:1.2.0-2
ii  libxdamage1          1:1.1.5-1
ii  libxext6             2:1.3.3-1+b2
ii  libxfixes3           1:5.0.3-1
ii  libxi6               2:1.7.9-1
ii  libxml2              2.9.4+dfsg1-7+b3
ii  libxrandr2           2:1.5.1-1
ii  libxrender1          1:0.9.10-1
ii  libxslt1.1           1.1.32-2
ii  libxss1              1:1.2.3-1
ii  libxtst6             2:1.2.3-1
ii  zlib1g               1:1.2.11.dfsg-1

Versions of packages chromium recommends:
ii  chromium-sandbox  76.0.3809.71-1

Versions of packages chromium suggests:
pn  chromium-driver  <none>
pn  chromium-l10n    <none>
pn  chromium-shell   <none>

Versions of packages chromium-common depends on:
ii  x11-utils  7.7+4
ii  xdg-utils  1.1.3-1

Versions of packages chromium-common recommends:
ii  chromium-sandbox                     76.0.3809.71-1
ii  fonts-liberation                     1:1.07.4-10
ii  libgl1-mesa-dri                      18.3.6-2
ii  libu2f-udev                          1.1.10-1
ii  notification-daemon                  3.20.0-4
ii  system-config-printer                1.5.11-4
ii  upower                               0.99.10-1
ii  xfce4-notifyd [notification-daemon]  0.4.4-1

Versions of packages chromium-sandbox depends on:
ii  libatomic1  9.1.0-10
ii  libc6       2.28-10
ii  libgcc1     1:9.1.0-10
ii  libstdc++6  9.1.0-10

-- no debconf information

--- End Message ---
--- Begin Message ---
Great, thank you for letting me know!

Ximin, if this is still an issue for you then please reopen. Otherwise, closing as fixed.


On Mon, 21 Mar 2022 08:38:42 -0300 Gabriel <[email protected]> wrote:
> Hi All
> Iǘe just tested that in my pc
>
> Versión 90.0.4430.212 (Build para desarrolladores) built on Debian 10.9,
> running on Debian 10.11 (64 bits)
>
> and works fine
>
> Cheers
> Gabriel
>
> El 20/3/22 a las 04:19, Andres Salomon escribió:
> >
> > Hi,
> >
> > Can you tell me if this issue is resolved with the latest chromium
> > (v99) or not?
> >
> > Thanks,
> >
> > Andres
> >
> >
> > On Tue, 06 Aug 2019 01:08:00 -0700 Ximin Luo wrote:
> >
> > > Package: chromium
> > > Version: 76.0.3809.87-2+b1
> > > Severity: important
> > >
> > > Dear Maintainer,
> > >
> > > Chromium can't access the microphone, the result is the same from
> > multiple websites
> > > (meet.jit.si, appear.in, google meet, etc)
> > >
> > > When visiting
> > https://webrtc.github.io/samples/src/content/getusermedia/volume/
> > > the console says:
> > >
> > > navigator.MediaDevices.getUserMedia error: Requested device not
> > found NotFoundError
> > >
> > > Note that this bug is separate from #923028, I do not see any
> > console messages about
> > > "not allowed to start", the audio device(s) themselves are invisible
> > to chromium.
> > >
> > > I have looked in the following files:
> > >
> > > /etc/chromium/master_preferences
> > > /usr/share/chromium/master_preferences
> > > ~/.config/chromium/Default/Preferences
> > >
> > > and there is no key "audio_capture_enabled" anywhere. So the issue
> > seems distinct
> > > from #885155 #884887 #889067 as well.
> > >
> > > X
> > >
> > >

--- End Message ---

Reply via email to