Zed Explorer stuck "Waiting for Camera" on Ubuntu 20.04 when running zed-docker
Bortronx opened this issue · comments
Preliminary Checks
- This issue is not a duplicate. Before opening a new issue, please search existing issues.
- This issue is not a question, feature request, or anything other than a bug report directly related to this project.
Description
After following the steps on the Install Guide
when launching ZED Explorer with the camera connected there is no camera feed input. The camera works fine and is detected by Ubuntu. The docker container is in --privileged mode.
I am using the following command to run it:
sudo docker run -it --gpus all --privileged -e DISPLAY -v /tmp/.X11-unix:/tmp/.X11-unix stereolabs/zed:3.6-gl-devel-cuda11.4-ubuntu20.04
and tried adding --device=/dev/video0
sudo docker run -it --gpus all --privileged --device=/dev/video0 -e DISPLAY -v /tmp/.X11-unix:/tmp/.X11-unix stereolabs/zed:3.6-gl-devel-cuda11.4-ubuntu20.04
Zed Explorer opens but black. No video feed.
Nvidia cuda docker is installed and running. Everything works but no camera is detected.
Steps to Reproduce
- Follow Installation guide Install Guide
- Open ZED_Explorer using
/usr/local/zed/tools/ZED_Explorer - Wait for Opening message
...
Expected Result
Camera Feed on ZED_Explorer
Actual Result
No Camera Feed on ZED_Explorer window
ZED Camera model
ZED Mini
Environment
OS: Ubuntu 20.04
CPU: Intel CORE i7-9750H 9th Gen x86_64
GPU: Nvidia GP107GLM Quadro P1000 Mobile
ZED SDK version: v3.6.0
Other: USB 3.0Anything else?
When it says "Waiting for Camera" in the ZED_Explorer if I unplug the camera it then says "Camera not detected". Meaning it's detecting the Camera but is not showing any feed just stuck "Waiting for Camera"
lsusb on the docker container returns:
Bus 002 Device 019: ID 2b03:f682 Technologies, Inc. ZED-M
Bus 001 Device 007: ID 2b03:F681STEREOLABS ZED-M Hid Device
This same camera shows up in the installation of ZEDSDK on Windows when launching ZED_Explorer.
Hi,
Just to make sure, Does ZED Explorer works when not in docker ? To make sure the problem is not on the camera itself.
Normally lsusb in container should give you 2 devices :
2b03:F682 --> ZED-M video controller
2b03:F681 --> ZED-M sensor controller
Can you check?
Hello!
thank you for the help. I get both in lsusb the second one shows as following:
Bus 001 Device 007: ID 2b03:F681STEREOLABS ZED-M Hid Device
ZED Explorer works in Windows on the same machine but different partition. Also I can see the camera feed fine using cheese outside of my zed-docker container. The problem is when using docker specifically.
I have run into the same thing and I suspect it may be due to a very recent upgrade because my camera was working fine yesterday and after doing what I thought was going to be a routine upgrade it stopped working (camera not detected). The camera does work on my jetson, so I know it is not the camera and it is not the docker setup (doesn't work outside of docker either).
Hi,
It seems the latest Ubuntu update upgraded the v4l2 driver and it changed the way it handles a parameter, hence breaking the connection with the ZED cameras.
The problem has been identified and we will release the patch v3.6.5 as soon as the QA tests are completed.
The fix will be available to download in the next few day.
Just to let you know that the docker images are also up to date with 3.6.5 now. You may have to re-pull manually the 3.6 tags
Everything works for me, so feel free to close this. Thanks again for your quick reponse!
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment otherwise it will be automatically closed in 5 days