Closed Bug 1758970 Opened 3 years ago Closed 3 years ago

Google Meet participant audio is not audible anymore

Categories

(Core :: WebRTC: Audio/Video, defect)

Firefox 100
x86_64
Linux
defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox100 --- affected

People

(Reporter: nagisa, Unassigned)

Details

This is a regression between some nightly in Firefox 99 series and Firefox 100.

People in a Google Meet room are not audible, even though audio from the browser otherwise works: music plays, various notification sounds from google meet page also work (e.g. chat notification sound or hand raised sound.)

Reverting back to some build of 99.0a1 makes it work just fine again.

Checksum of first known bad build: bb76a3e1411f43b698a0b9c59a6e93ca1e73db3cacfb73eadf6a19db4de9c758 (2022-03-09)
Last known to me good build: d3d8cc1dad30db4616919f3f0c2e8a7264b8458df3fb45ee77daa080ec5e9e5e

Severity: -- → S4
Priority: -- → P3
Component: General → WebRTC: Audio/Video

The component has been changed since the backlog priority was decided, so we're resetting it.
For more information, please visit auto_nag documentation.

Priority: P3 → --

Could you please try using mozregression to find a regression range? Thanks!

https://mozilla.github.io/mozregression/

Flags: needinfo?(simonas+bugzilla.mozilla.org)

I tried using mozregression in the past but wasn't able to make it work on my system (NixOS). Are there any instructions on how to bisect more manually? I effectively need just a description of where I can find dated artifacts.

Worked for me today with the nightly from March 11th, so might have been an issue on Google side, or fixed between 03-09 and 03-11 on the firefox side.

Status: NEW → RESOLVED
Closed: 3 years ago
Flags: needinfo?(simonas+bugzilla.mozilla.org)
Resolution: --- → WORKSFORME
No longer blocks: webrtc-triage
You need to log in before you can comment on or make changes to this bug.