[gstreamer-bugs] [Bug 588078] [playbin2] Fails to go to READY again after an error

[GStreamer (bugzilla.gnome.org)]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=588078

  GStreamer | gst-plugins-base | Ver: git

Sebastian Dröge changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #138198|none                        |committed
               Flag|                            |
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |FIXED




------- Comment #6 from Sebastian Dröge  2009-07-10 15:12 UTC -------
commit 3d751d190d89c10210d2bf0dd4c6019bd4ddc217
Author: Sebastian Dröge <sebastian.droege at collabora.co.uk>
Date:   Fri Jul 10 17:08:40 2009 +0200

    playbin2: Make it possible for READY->PAUSED to succeed after it failed the 

    If READY->PAUSED failed in the source element we would've swapped
    the current and next group already. To allow READY->PAUSED to succeed
    after the first failure we have to swap the current and next group
    back again. This also ensure that we're again in the same state
    as before the failed state change and not at the next group.

    This was especially a problem for playbin2 pipelines that use the
    new mounting support in giosrc as the source would fail for READY->PAUSED
    the first time, the application mounts the location and then tries
    to go READY->PAUSED again (and this time it would succeed).

    Fixes bug #588078.


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=588078.