Your message dated Wed, 7 Sep 2022 09:32:48 +0100
with message-id <[email protected]>
and subject line Re: Audio capture (e.g., in MS Teams) doesn't work
has caused the Debian Bug report #1019263,
regarding chromium: Audio capture (e.g., in MS Teams) doesn't work
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.)
--
1019263: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019263
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: chromium
Version: 105.0.5195.102-1
Severity: normal
X-Debbugs-Cc: [email protected]
When I try to join a Teams meeting, I get the mesasge
Are you sure you don't want audio or video? If you change your mind,
select the camera icon by your address bar and then _Always allow_.
This appears to happen because Teams can't see the existance of my
microphone. When I click the camera icon in the address bar, I see:
Camera and Microphone Blocked
This page has been blocked from accessing your camera and micrphone.
( ) Always allow https://teams.microsoft.com to access your camera and
microphone
(x) Continue blocking camera and microphone access
Microphone: Default
Camera: TOSHIBA Web Cam...
[Manage] [Done]
Now the funny things about this popup are:
* Selecting 'always allow' and pressing Done doesn't work. If I click
the camera icon again, the popup comes back and 'always allow' is
selected, but Teams behaves as if I didn't change the option and
continued to block it.
* If I reload the page and join another meeting, 'Continue blocking' is
set, so chromium doesn't remember my selection between page loads.
* When I try to change the devices listed in the popup, by clicking on
what I assume is supposed to be a dropdown menu, nothing happens;
it's as if the widget is disabled, though there is no visual
indication of such
* If I press Manage, it takes me to
<chrome://settings/content#media-stream-mic> which has an entry right
at the top of 'recent activity' saying: teams.microsoft.com: Allowed
camera, microphone
* If I click on this entry it takes me to
<chrome://settings/content/siteDetails?site=https%3A%2F%2Fteams.microsoft.com%2F>
which under 'permissions' has Microphone set to Block. If I click
this I get a dropdown menu with the entries Block (default), Allow
and Block. If I choose Allow in this dropdown menu, the choice is
instantly reset back to Block.
Trying to debug this at another site,
<https://webrtc.github.io/samples/src/content/getusermedia/volume/>,
when I press 'Start' I get the same popup as with Teams (although this
one doesn't mention the camera being blocked). This one has the same
behaviour: 'Continue blocking' is selected by default, if I change it to
'allow' and press 'Done', nothing happens. If I reload the page, next
time I click the camera icon to get the popup, 'Continue blocking' is
still set.
In the console, these messages are logged when I press 'Start'.
Requesting local stream
main.js:56 navigator.MediaDevices.getUserMedia error: Permission denied
NotAllowedError
-- System Information:
Debian Release: 11.4
APT prefers stable-updates
APT policy: (570, 'stable-updates'), (570, 'stable-security'), (570,
'stable-debug'), (570, 'stable'), (550, 'testing-debug'), (550, 'testing'),
(530, 'unstable-debug'), (530, 'unstable'), (1, 'experimental-debug'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.18.0-3-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_USER, TAINT_DIE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: default
Versions of packages chromium depends on:
ii chromium-common 105.0.5195.102-1
ii libasound2 1.2.7.2-1
ii libatk-bridge2.0-0 2.38.0-1
ii libatk1.0-0 2.36.0-2
ii libatomic1 12.2.0-1
ii libatspi2.0-0 2.38.0-4
ii libbrotli1 1.0.9-2+b2
ii libc6 2.34-4
ii libcairo2 1.16.0-5
ii libcups2 2.4.2-1+b1
ii libdbus-1-3 1.12.20-2
ii libdouble-conversion3 3.1.5-6.1
ii libdrm2 2.4.104-1
ii libevent-2.1-7 2.1.12-stable-1
ii libexpat1 2.2.10-2+deb11u3
ii libflac8 1.3.3-2+deb11u1
ii libfontconfig1 2.13.1-4.2
ii libfreetype6 2.12.1+dfsg-3
ii libgbm1 20.3.5-1
ii libgcc-s1 12.2.0-1
ii libglib2.0-0 2.72.3-1+b1
ii libgtk-3-0 3.24.34-3
ii libjpeg62-turbo 1:2.0.6-4
ii libjsoncpp25 1.9.5-4
ii liblcms2-2 2.12~rc1-2
ii libminizip1 1.1-8+b1
ii libnspr4 2:4.34.1-1
ii libnss3 2:3.82-1
ii libopenjp2-7 2.4.0-3
ii libopus0 1.3.1-0.1
ii libpango-1.0-0 1.50.9+ds-1
ii libpng16-16 1.6.37-3
ii libpulse0 14.2-2
ii libre2-9 20210201+dfsg-1
ii libsnappy1v5 1.1.9-2
ii libstdc++6 12.2.0-1
ii libwayland-client0 1.21.0-1
ii libwebp7 1.2.2-2+b1
ii libwebpdemux2 1.2.2-2+b1
ii libwebpmux3 1.2.2-2+b1
ii libwoff1 1.0.2-1+b1
ii libx11-6 2:1.8.1-2
ii libxcb1 1.14-3
ii libxcomposite1 1:0.4.5-1
ii libxdamage1 1:1.1.5-2
ii libxext6 2:1.3.3-1.1
ii libxfixes3 1:6.0.0-1
ii libxkbcommon0 1.0.3-2
ii libxml2 2.9.14+dfsg-1+b1
ii libxnvctrl0 470.103.01-1~deb11u1
ii libxrandr2 2:1.5.1-1
ii libxslt1.1 1.1.34-4+deb11u1
ii xdg-desktop-portal-gnome [xdg-desktop-portal-backe 42.3-1+b1
ii xdg-desktop-portal-gtk [xdg-desktop-portal-backend 1.14.0-1
ii zlib1g 1:1.2.11.dfsg-2+deb11u2
Versions of packages chromium recommends:
ii chromium-sandbox 105.0.5195.102-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 libc6 2.34-4
ii libdouble-conversion3 3.1.5-6.1
ii libstdc++6 12.2.0-1
ii libx11-6 2:1.8.1-2
ii libxnvctrl0 470.103.01-1~deb11u1
ii x11-utils 7.7+5
ii xdg-utils 1.1.3-4.1
ii zlib1g 1:1.2.11.dfsg-2+deb11u2
Versions of packages chromium-common recommends:
ii chromium-sandbox 105.0.5195.102-1
ii fonts-liberation 1:1.07.4-11
ii gnome-shell [notification-daemon] 42.4-1+b1
ii libgl1-mesa-dri 20.3.5-1
ii libu2f-udev 1.1.10-3
ii notification-daemon 3.20.0-4
ii system-config-printer 1.5.14-1
ii upower 0.99.20-1
Versions of packages chromium-sandbox depends on:
ii libc6 2.34-4
-- Configuration Files:
/etc/chromium/policies/recommended/duckduckgo.json [Errno 2] No such file or
directory: '/etc/chromium/policies/recommended/duckduckgo.json'
-- no debconf information
--- End Message ---
--- Begin Message ---
It turns out this was caused by the audio_capture_enable setting which
made its way into my profile.
--
Sam Morris <https://robots.org.uk/>
PGP: rsa4096/CAAA AA1A CA69 A83A 892B 1855 D20B 4202 5CDA 27B9
--- End Message ---
