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 622967 - [queue2] Problems with progressive downloading
[queue2] Problems with progressive downloading
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
git master
Other Linux
: Normal blocker
: 0.10.30
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Reported: 2010-06-27 17:52 UTC by Sebastian Dröge (slomo)
Modified: 2010-06-29 11:17 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description Sebastian Dröge (slomo) 2010-06-27 17:52:34 UTC
Since this commit the webm YouTube videos don't work anymore, most probably because matroskademux can't get a positive answer from the position query. Disabling progressive downloading for webm fixes it, or reverting this commit.

commit 0a84d8190138c82f74fe7276a6b6dc54a0a4f3a8
Author: Wim Taymans <>
Date:   Mon Jun 21 11:41:46 2010 +0200

    queue2: fix merging of ranges
    When we merge two ranges, don't updata the current range writing_pos with
    whereever we were writing earlier in the merged range.  Spotted by bilboed.
Comment 1 Wim Taymans 2010-06-28 08:45:24 UTC
do you have an example link with a video?
Comment 2 Sebastian Dröge (slomo) 2010-06-28 09:02:14 UTC
Comment 3 Sebastian Dröge (slomo) 2010-06-28 09:02:47 UTC
It doesn't happen always but in >50% of the tries btw.
Comment 4 Wim Taymans 2010-06-28 10:05:37 UTC
does this pipeline fail as well?

gst-launch playbin2 flags=0x97 uri=""
Comment 5 Benjamin Otte (Company) 2010-06-28 10:52:12 UTC
The t= flag in Youtube videos is a per-user token and only valid for 10 or so minutes and IP-bound iirc. So that link will not work for anyone else.

You can copy a token and replace it in the link above using view source in your browser though.
Comment 6 Sebastian Dröge (slomo) 2010-06-29 05:01:54 UTC
This seems to be a problem in WebKit's HTTP source and state handling. I fixed the HTTP source already, now
Comment 7 Sebastian Dröge (slomo) 2010-06-29 11:17:35 UTC
Yes, webkit problem.