[DRE-maint] [Bug 304080] Re: Inconsistent state return by ruby binding for gstreamer

[William Van Hevelingen]

I just tested the example script in Lucid and can verify the same error
in lucid.

** Summary changed:

- [Intrepid] Inconsistent state return by ruby binding for gstreamer
+ Inconsistent state return by ruby binding for gstreamer

** Changed in: ruby-gstreamer0.10 (Ubuntu)
       Status: New => Confirmed

-- 
You received this bug notification because you are subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/304080

Title:
  Inconsistent state return by ruby binding for gstreamer

Status in “ruby-gstreamer0.10” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: libgstreamer0.10-ruby1.8

  Hi.

  I use libgstreamer0.10-ruby1.8 (0.2.0-4) to play audio file (ogg, mp3). Since the upgrade to intrepid I have inconsistent behaviour.
  Sometimes, everything works fine.
  I have sometimes an error:
  GStreamer-CRITICAL **: gst_element_set_state: assertion `GST_IS_ELEMENT (element)' failed
  Sometimes, no sound is played by gstreamer.

  It seems that the state return by different methods (ready, play, stop) is inconsistent:
  #<Gst::Element::StateReturn STATE>
  where STATE stands for failure, async, success or a integer.

  The behaviour of gstreamer seems not correlated with the returned
  state. The file can be played even if the state is failure...

  I have attach a small code to show the bug. Just run the script with
  an absolute path to an audio file as argument. The file should be
  played 10 times for 3 seconds. Current state is written to standart
  ouput.

  With the 0.2.0-3 version on hardy, the example return the expected
  state.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ruby-gstreamer0.10/+bug/304080/+subscriptions