[Bug 704555] hlsdemux: cannot register existing type GstFragment when using encrypted HLS streams

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=704555
  GStreamer | gst-plugins-bad | git

Tim-Philipp Müller <t.i.m> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
                 CC|                            |t.i.m at zen.co.uk
         Resolution|                            |FIXED
   Target Milestone|HEAD                        |1.1.3
            Summary|assert failure when using   |hlsdemux: cannot register
                   |encrypted HLS streams       |existing type GstFragment
                   |                            |when using encrypted HLS
                   |                            |streams

--- Comment #1 from Tim-Philipp Müller <t.i.m at zen.co.uk> 2013-07-22 13:58:25 UTC ---
Thanks, pushed:

 commit ed16c9c560afb5feac1632a33e4d7fbde621eca0
 Author: Alex Ashley <bugzilla at ashley-family.net>
 Date:   Fri Jul 19 15:30:42 2013 +0100

    hls: fix for assert failure when using encrypted HLS streams

    When using an HLS encrypted stream, an assertion failure is thrown:
    (gst-launch-1.0:31028): GLib-GObject-WARNING **: cannot register
    existing type `GstFragment'

    (gst-launch-1.0:31028): GLib-CRITICAL **: g_once_init_leave: assertion
    `result != 0' failed

    Eventually tracked this down to the call gst_fragment_new()
    in function gst_hls_demux_decrypt_fragment.

    The GstFragment class is defined in ext/hls/gstfragment.c and in
    gst-libs/gst/uridownloader/gstfragment.c. Having two class definitions
    with the same name causes the assert failure when trying to allocate
    GstFragment. Deleting the version from hls and editing the
    Makefile.am solves this assert failure.

    https://bugzilla.gnome.org/show_bug.cgi?id=704555


(this silly little mini-library should just go away, but that's independent of
this issue of course).

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.