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 524789 - Could not get buffers from device /dev/video0
Could not get buffers from device /dev/video0
Status: RESOLVED DUPLICATE of bug 467214
Product: GStreamer
Classification: Platform
Component: gst-plugins-good
0.10.14
Other Linux
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-03-28 13:32 UTC by claudiohfg
Modified: 2008-03-31 08:38 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description claudiohfg 2008-03-28 13:32:53 UTC 
I'm trying to access my webcam through gstreamer-properties, but it fails:

$ gstreamer-properties 
gstreamer-properties-Message: Skipping unavailable plugin 'artsdsink'
gstreamer-properties-Message: Skipping unavailable plugin 'pulsesink'
gstreamer-properties-Message: Skipping unavailable plugin 'v4lmjpegsrc'
gstreamer-properties-Message: Skipping unavailable plugin 'qcamsrc'
OIL: ERROR liboiltest.c 403: oil_test_check_impl(): function sad8x8_8xn_u8_psadbw in class sad8x8_8xn_u8 failed check (245674 > 0) || (outside=0)
gstreamer-properties-Message: Skipping unavailable plugin 'esdmon'
gstreamer-properties-Message: Skipping unavailable plugin 'pulsesrc'
gstreamer-properties-Message: Error running pipeline 'Video for Linux 2 (v4l2)': Could not get buffers from device '/dev/video0'. [v4l2src_calls.c(1025): gst_v4l2src_capture_init (): /pipeline0/v4l2src3:
error requesting 0 buffers: Can not allocate memory]
Comment 1 Tim-Philipp Müller 2008-03-31 08:38:50 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 467214 ***