[Gstreamer-bugs] [Bug 90885] Changed - set_state(READY) wont work on my machine

[bugzilla-daemon at widget.gnome.org]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

http://bugzilla.gnome.org/show_bug.cgi?id=90885

Changed by thomas at urgent.rug.ac.be.

--- shadow/90885	Thu Aug 15 17:48:55 2002
+++ shadow/90885.tmp.25018	Sat Aug 17 13:59:11 2002
@@ -1,12 +1,12 @@
 Bug#: 90885
 Product: GStreamer
 Version: 0.4.0
 OS: Linux
 OS Details: SuSE 7.2 (kernel 2.4.4)
-Status: NEW   
+Status: NEEDINFO   
 Resolution: 
 Severity: normal
 Priority: Normal
 Component: gstreamer (core)
 AssignedTo: gstreamer-maint at bugzilla.gnome.org                            
 ReportedBy: florianbe at aec.at               
@@ -56,6 +56,15 @@
 DEBUG( 1859: 0)gst_element_set_state:1829: [work_thread] setting state 
 from NULL to READY
 INFO ( 1859: 0)gst_thread_change_state:258: [work_thread] sync(0): 
 changing state from NULL to READYDEBUG( 1859: 
 0)gst_thread_change_state:272: [work_thread] sync(0): creating thread 
 "work_thread"
+
+------- Additional Comments From thomas at urgent.rug.ac.be  2002-08-17 13:59 -------
+out of curiosity, why do you set it to PLAYING twice in a row ?
+My hunch is that we have a race condition there; you're trying to set
+it to PLAYING, and the core signals the thread to go to PLAY, but it's
+not done by the time the second _set starts.
+
+It's something that should be fixed in any case, but please try with
+only one set to PLAY and let us know how that changes things.