Closed TomTruyen closed 1 month ago
Could you check if this issue is also present in regular firefox browser? I've had people have a similar browser issue with google meet where they couldn't use it in firefox but it worked perfectly fine in chrome.
I just checked. This is also an issue on Firefox. Though it can't be that this is just a feature, is there some setting or about:config
that can be set to fix it?
@TomTruyen Sadly, I don't have a mac anymore. I daily drive linux and windows with firefox 129(now zen browser) and It's not an issue for me. So, I can't really debug it for you. However, you can check the firefox bugzilla for this issue or create one there.
Meanwhile, use chrome/chromium just for meetings. You could also check if other options like Zoom work fine on firefox just to confirm that the issue is with firefox or google meet before creating an issue on firefox bugzilla.
As noted in this Moz question forum looks like the issue is likely due to privacy / security configuration on your Firefox. It often breaks in brave too so I'd temporarily disable them just for meet.google.com
domain.
The question forum linked above seems to relate to inability to share certain windows, unrelated to this.
+1 to the issue. I am trying to migrate to Zen (from Arc) on my work laptop (Mac M2) and whenever joining the meeting, I can see the list of participants, but none of their video cams are loaded in (I just see their avatar consisting of a letter) and I cannot hear the participants. After a minute or two, Google meet drops me. Worth noting when an external user tries to connect to the external meeting, an "admit" window is supposed to appear. On Zen browser it does not happen, as if it doesn't connect to the RTC/websocket server at all.
@meguroyama comment had me try adding meet.google.com to the exception list for these options: I also tried to disable the custom DNS resolution: None of these worked.
Some of items of interest in the console: (uBlock Origin disabled at moment of screenshot)
Screenshot when I get dropped:
Extensions I run: uBlock Origin 1 Password I still don't care about cookies
For all of the above tests, I have disabled all of my extensions to no avail.
Went into about:webrtc and noticed it couldn't resolve the some of the addresses.
After googling a bit, and going back-and-forth between issues from years ago, I took a look at about:config
and I noticed media.peerconnection.ice.default_address_only
setting which was set to true
- I set it to False, and suddenly google meet started working (with uBlock Origin enabled as well)! :) @TomTruyen, you were looking for a setting that could fix it - this potentially could be a fix for you.
According to https://wiki.mozilla.org/Media/WebRTC/Privacy, media.peerconnection.ice.default_address_only
is by default set to false
- Not sure why this would be true by default in Zen, but I am not familiar at all with WebRTC, TURN servers or whatever. It's worth nothing that I am on a corporate VPN network, as I would be using Zen on a work-laptop. Maybe the custom network profile settings interfere with the TURN server reach-ability.
I can also see that the uBlock Origin, in the past, might have modified some of the WebRTC settings. However most of my tests were carried out without the extensions enabled.
Final configuration that seems to work for me:
Looks like this change was propagated down to Zen by bundling "Betterfox" with Zen https://github.com/yokoffing/Betterfox Line responsible for setting this preference config to true can be found here. https://github.com/zen-browser/desktop/blob/ad95eed29fe566430ff776e68e902788b3262299/src/browser/app/profile/better-fox.js#L109
Please dont just put "1.0.0" as the version number, now I dont know when it started happening
Looks like this change was propagated down to Zen by bundling "Betterfox" with Zen https://github.com/yokoffing/Betterfox Line responsible for setting this preference config to true can be found here.
Should I remove it?
What happened?
When using Google Meet on my Mac with Zen:
Expect: Google Meet should work as it does on other browsers
Workaround: Use a different browser for Google Meet :(
Reproducible?
Version
1.0.0
Severity impact
High
What platform are you seeing the problem on?
macOS - aarch64
Relevant log output
No response