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 733596 - [REGRESSION] gst-discoverer timeouts on some files
[REGRESSION] gst-discoverer timeouts on some files
Status: RESOLVED DUPLICATE of bug 733495
Product: GStreamer
Classification: Platform
Component: gst-plugins-base
git master
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2014-07-23 08:50 UTC by Thibault Saunier
Modified: 2014-07-23 08:57 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Thibault Saunier 2014-07-23 08:50:01 UTC 
After that commit I can notice that some files are not discoverable anymore (attaching one here). The problem is that we never see ASYNC_DONE on the bus. It looks like there are 2 ASYNC_START message in the list of messages of the discoverer-uri uridecodebin.

The faulty commit is:

commit c051b378d7405d41b0de096cf64451a667864acc
Author: Sebastian Dröge <sebastian@centricular.com>
Date:   Tue Jul 15 17:23:24 2014 +0200

    uridecodebin: Create new sources after chaining up to the parent class
    
    Otherwise we start the new sources already before the parent class
    got ready to start.

That broke our gst-validate testsuite: https://jenkins.arracacha.collabora.co.uk/view/pitivi/job/gst-validate-tests/740/
Comment 1 Tim-Philipp Müller 2014-07-23 08:57:36 UTC 

*** This bug has been marked as a duplicate of bug 733495 ***
Comment 2 Sebastian Dröge (slomo) 2014-07-23 08:57:58 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.