-
Notifications
You must be signed in to change notification settings - Fork 530
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Device lose video capture capability! #600
Comments
|
Thanks for the replay, |
also i checked the latest version and the problem still there. |
that was really just an example. e.g. in your example there is no a producer anywhere. |
You can take a look at kasm application (https://kasmweb.com/) |
sorry, I don't think i will (find the time to) checkout kasm, just to reproduce this issue. please try to provide a minimal reproducible example. |
Is there an existing issue for this?
Detail
I am using v4l2loopback for webcam as a virtual device in container for chrome application.
Here is the scenario:
1- i build the source and load the devices with exclusive_caps
2- i run the container and map the device into container using --device flag
3- open the webcam test in chrome and everything is fine
4- delete the container and run again
5- that device no longer known as a webcam or capture device!!
I run v4l2-ctl device=/dev/video2 --all before and after using it in container and find out after destroy the container the device lose it's capture device capability!!
Here is the log before i run container at fresh loading:
And this is after i remove the container:
What is wrong? what is modifying the device? how can i resolve this?
v4l2loopback version
0.12.5
kernel version
OS Version
Ubuntu 20.04
Which CPU are you using?
amd64/x86_64 ("64bit Intel")
The text was updated successfully, but these errors were encountered: