Camera and Mic acces
- Min Version: 1.22.2
- Operating system: Linux Ubuntu 20.4
Expected Behavior
The Browser should ask for camera and mic access when trying to open/join a google.meet
Actual Behavior
Right now the browser doesn't ask the user to give access so you can't basically go in a meeting(and also there is no way to enable them manually(at least I couldn't find anything)
I think this might have been fixed in a1580c8a9aafd6aa44f5a81fb82b85ddf4d68eb4; can you try again after the next release soon?
Works without any problems on the latest version of Min on Ubuntu 20.04.4 x86 Can be closed
Issue is solved!
Jan 27th, 2023 Min v1.31.1 Chromium v121.0.6159.0 Ubuntu 22.0.4 LTS
When on a meet.google.com session, access to Mic and Camera are blocked. The session does not pop up a dialogue to allow user to permit access to either resource. Instead it provides a how to pop up indicating to select an icon by the URL to allow access to mic and camera. This icon is not available nor is it available from any menu on the minbrowser.
Either this icon needs to be shown on the browser for permissions access, or a pop-up requesting access needs to occur. I have also checked the preferences to see if pop-ups were being suppressed or blocked, but did not find any settings specific for this.
I made a user script workaround:
// ==UserScript==
// @name Google Meet A/V Permissions
// @match https*://meet.google.com
// @run-at document-start
// ==/UserScript==
navigator.mediaDevices.getUserMedia({ video: true, audio: true })
I put that in a file userscripts/google-meet-permissions.js, and now every time I visit Google Meet, the mic and camera permissions button appears in the tab as expected.
This seems like a limitation of Electron - electron/electron#36232.
In Meet, I'm seeing repeated calls to permissionCheckHandler. In Chrome, these normally indicate that a prompt can be shown:
But Electron only supports returning true/false, which correspond to granted/denied, so Meet never attempts to request the permission:
The workaround from @wong-justin forces the permission request to actually happen, which gives the user an opportunity to grant it.
Hey guys. having a similar problem biut with element and jitsi.
Nice idea on the script- it certainly got the session pop up to appear for me. and i can click allow, however, the result is still the same... has anyone got any further ideas ??
I can see in the console. that RTCutils has found the input device info (in spite of this you can't select or choose anything in the browser) with ultimately the message gum.permission_denied
I've added @wong-justin's workaround to the built-in workaround list, which should fix Google Meet for now (24363eccdf7242f403d2cd95362ea69c136083c6). Thanks for the idea!
The Element and Jitsi issue has a different cause - #2502 - so I think this issue is resolved now.