Closed Bug 1407569 Opened 8 years ago Closed 6 years ago

Google Meet unable to acquire camera

Categories

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

defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: marco, Unassigned)

References

(Blocks 1 open bug)

Details

STR: 1) Start a call on Google Meet 2) Camera prompt appears 3) Accept prompt 4) The camera turns on and quickly turns off again (I can see the led indicator flashing once). 5) The prompt appears again, go to step 2.
I have seen this as well. The current theory from :drno and myself is that this is a bug in Meet, but we need to track it down. Maybe a job for webcompat?
Flags: needinfo?(drno)
Thanks Marco. Yeah since Thursday I'm encountering the same problem. Sometimes it doesn't even ask for camera at all. Everything was working fine for me before. Plus all other WebRTC services appear to work fine. So I assume this is some JS issue in Google's code at this point. I contacted the Google hangout folks directly about this.
Flags: needinfo?(drno)
Rank: 35
Priority: -- → P3
Just for the record, I can still reproduce this. Sometimes, it asks for microphone permissions and then the audio works, but I never saw any Webcam permission prompt. Also, I am unable to find the cause of why it "sometimes" works and sometimes doesn't from a quick look. :/
This issue continues for me as well in Firefox 62 on MacOS. When starting a meeting the audio permission always appears, but not the video (I'm using an external webcam on a MacBook Pro). The screen says "Camera is starting". Testing in Chrome the camera permission dialog appears right away. Also worth noting that after I've tested in Chrome, going back to Firefox the camera permission dialog works as expected.
Blocks: meet

So, I was just able to perform a call without any trouble, including webcam support. Marco, can you confirm it's working now? :)

Flags: needinfo?(mcastelluccio)

I haven't been able to reproduce for a while.

Status: NEW → RESOLVED
Closed: 6 years ago
Flags: needinfo?(mcastelluccio)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.