GNOME Bugzilla – Bug 744135
gst-plugins-good-1.4.5: v4l2 plugin tries to access /dev/video0 when gst-plugin-scanner -l is run
Last modified: 2015-02-07 18:30:12 UTC
Created attachment 296334 [details] build.log On Gentoo we run compilations inside a sandbox system to prevent unwanted access to files and devices from "real" system. That way, we are getting now errors on some packages when gst-plugin-scanner is run as it wants to access to /dev/video0 directly. Looks like this is caused by the v4l2 plugin as we only get the error when it's present. I am unsure if it's normal that the plugin tries to write to that device when gst-plugins-scanner checks for its existence :/ The attached full build.log is from farstream-0.2.6, whose building calls gst-plugin-scanner and hits this problem Thanks a lot
It is a false positive in your security measure. The plugin scans for fixed devices like decoders in order to create specific element dynamically for them. In the end, on most PCs, nothing will be created since they don't have HW decoder with V4L2 M2M driver. I doubt opening the device node in readonly would make any sense here.