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 736748 - 1.4.1 regression: textoverlay: Internal data flow error with decodebin
1.4.1 regression: textoverlay: Internal data flow error with decodebin
Status: RESOLVED DUPLICATE of bug 735844
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
1.4.1
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2014-09-16 14:02 UTC by Will Manley
Modified: 2014-09-16 14:32 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Will Manley 2014-09-16 14:02:21 UTC 
The following command fails:

    gst-launch-1.0 videotestsrc ! textoverlay ! decodebin ! video/x-raw \
                   ! fakesink

with the error:

    Setting pipeline to PAUSED ...
    Pipeline is PREROLLING ...
    ERROR: from element /GstPipeline:pipeline0/GstVideoTestSrc:videotestsrc0: Internal data flow error.
    Additional debug info:
    gstbasesrc.c(2933): gst_base_src_loop (): /GstPipeline:pipeline0/GstVideoTestSrc:videotestsrc0:
    streaming task paused, reason not-linked (-1)
    ERROR: pipeline doesn't want to preroll.
    Setting pipeline to NULL ...
    Freeing pipeline ...

Removing any one of "textoverlay", "decodebin" or "video/x-raw" allows the pipeline to run.  This seems to be a regression in 1.4.1 vs. 1.4.0.  I am using the GStreamer packages in debian stable version 1.4.1-1.1

I suspect this may be related to #733916 which I raised previously which relates to the `GstVideoOverlayComposition` mechanism.  I suspect this is the case as it was the same unit-test in my app that started failing. The workaround I put in my app for #733916 such that it would work with 1.4.0 no longer works with 1.4.1.  I have not yet done sufficient investigation to either narrow down the cause or work around the issue.
Comment 1 Sebastian Dröge (slomo) 2014-09-16 14:32:53 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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