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 672824 - [0.11] v4l2src exits with error unless num-buffers set
[0.11] v4l2src exits with error unless num-buffers set
Product: GStreamer
Classification: Platform
Component: gst-plugins-good
Other Linux
: Normal normal
: 0.11.3
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Reported: 2012-03-26 02:42 UTC by Tim McHugh
Modified: 2012-03-26 15:07 UTC
See Also:
GNOME target: ---
GNOME version: ---

Log output from test cases (5.20 KB, text/plain)
2012-03-26 02:43 UTC, Tim McHugh

Description Tim McHugh 2012-03-26 02:42:45 UTC
Works: gst-launch-0.11 --gst-debug=v4l*:4 v4l2src io-mode=1 num-buffers=5 ! autovideosink

Gives Error: gst-launch-0.11 --gst-debug=v4l*:4 v4l2src io-mode=1 ! autovideosink

ERROR: v4l2src gstv4l2src.c:822:gst_v4l2src_fill:<v4l2src0> error processing buffer

The same error also occurs in a Python application when calling:
Gst.Element.send_event(self.pipeline, Gst.Event.new_eos());

Tested variant pipelines in 0.10.35 which both work without error:
gst-launch --gst-debug=v4l*:3 v4l2src num-buffers=5 ! autovideosink
gst-launch --gst-debug=v4l*:3 v4l2src ! autovideosink

Note: The 0.10.35 tests work in MMAP mode as io-mode is new and the only way I could start a v4l2src in 0.11 per this bug:

See attached for debug info...
Comment 1 Tim McHugh 2012-03-26 02:43:33 UTC
Created attachment 210598 [details]
Log output from test cases
Comment 2 Wim Taymans 2012-03-26 15:07:53 UTC
commit 01838ff97512a8a97c12136f8095e5874ab46d2b
Author: Wim Taymans <>
Date:   Mon Mar 26 15:59:01 2012 +0200

    v4l2src: don't error in shutdown
    Don't log with the ERROR category when we are stopping because we are shutting