Missing placeholder video device from enumerateDevices()
Categories
(Core :: WebRTC: Audio/Video, defect)
Tracking
()
People
(Reporter: david.turner, Unassigned)
Details
Attachments
(1 file)
|
478 bytes,
text/html
|
Details |
Steps to reproduce:
- I'm testing with the latest bookmarks/central on an aarch64 Raspberry Pi 4 using Raspberry Pi OS bookworm (based on debian bookworm).
- The system has 5 V4L2 video capture devices, 2 audio capture devices, and 1 pipewire/libcamera video capture device.
media.webrtc.camera.allow-pipewireis set to true.- The mozilla GUM camera test detects all the devices and the pipewire webcam works fine.
I open a fresh Firefox instance and run the attached reproducer.
Actual results:
I see 2 audio devices and no video devices. The exact output is:
Device type audioinput: id ZmB7s+AFwLcVIFRzHPFq5E9btvLRqLqkQAbQ+Su5nAc= label ''
Device type audioinput: id 7wXgfY4cCVbxIZMfotGurMHa8LJOlQTkny4Ik6fMcy8= label ''
Expected results:
I would expect to see two audio devices and one placeholder video device.
This is breaking Google Meet on this platform, because it sees no cameras available and so does not do a GUM request.
|
Reporter | |
Comment 1•11 months ago
|
||
CC Andreas: new bug as requested, and I've confirmed the issue still occurs with latest bookmarks/central. Please let me know if any other information or debugging would be useful.
|
|
Reporter | |
Comment 2•11 months ago
|
||
After reading https://jgrulich.cz/2023/11/24/pipewire-camera-support-in-firefox-2/ I decided to check my IsCameraPresent result from xdg-desktop-portal, and weirdly it's coming back as False, despite the pipewire webcam working just fine in the mozilla GUM test. So this might not actually be a Firefox bug - I'll dig into XDP and try to work out what's going on there.
|
|
Reporter | |
Comment 3•11 months ago
|
||
Confirmed that this is an XDP issue on my end (one of a long-running series of weird races between pipewire and xdg-desktop-portal). Sadly even when the placeholder appears correctly Google Meet still doesn't work, but it looks like that's Meet's fault rather than Firefox's, I don't think Meet correctly handles the placeholder device.
|
||
Comment 4•11 months ago
|
||
Indeed, see bug 1869042.
Description
•