After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 744135 - gst-plugins-good-1.4.5: v4l2 plugin tries to access /dev/video0 when gst-plugin-scanner -l is run
gst-plugins-good-1.4.5: v4l2 plugin tries to access /dev/video0 when gst-plug...
Product: GStreamer
Classification: Platform
Component: gst-plugins-good
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Reported: 2015-02-07 17:34 UTC by Pacho Ramos
Modified: 2015-02-07 18:30 UTC
See Also:
GNOME target: ---
GNOME version: ---

build.log (117.44 KB, text/plain)
2015-02-07 17:34 UTC, Pacho Ramos

Description Pacho Ramos 2015-02-07 17:34:15 UTC
Created attachment 296334 [details]

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
Comment 1 Nicolas Dufresne (ndufresne) 2015-02-07 18:30:12 UTC
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.