GNOME Bugzilla – Bug 466717
gst_event_new_new_segment_full:assertion `start <= stop' failed
Last modified: 2007-10-31 18:36:07 UTC
There is a new problem with playing sounds in gnome-games, using GStreamer
The following warning is printed to the console each time a sound is played.
(gnometris:16512): GStreamer-CRITICAL **: gst_event_new_new_segment_full:
assertion `start <= stop' failed
Base system is OpenSuSE 10.3 Beta 1, with the following packages:
The code is here:
Sound is played successfully the first time, then the next sounds are not
played correctly. This did not happen in previous versions of GStreamer.
You seem to have one playbin accessed by potentially many (10) threads.
Can you provide a GST_DEBUG=play*:5,decodebin:5 debug log? It should not be too large.
Created attachment 93785 [details]
Thanks for the interest in helping. The debug information is attached,
for when playing several seconds of gnometris.
It looks like oggdemux cannot deal with the very small ogg files.
* ext/vorbis/vorbisdec.c: (vorbis_dec_push_forward):
When calculating the first timestamp of the buffers, don't go below 0
and clip the samples because the offset was on the eos page.
* ext/ogg/gstoggdemux.c: (gst_ogg_demux_read_chain),
Also submit the eos page when trying to find the first timestamp.
Did you commit the changes to gstoggmux.c? I can't see them on webcvs...
OOops... I found it now. Thanks again.
I can still reproduce this problem with the GNOME 2.20.0 LiveCD (foresight-2.20.0-x86), downloaded from here: http://torrent.gnome.org/
Does this mean that it hasn't been fixed in Gstreamer yet, or that foresight-2.20.0 doesn't contain the latest releast of GStreamer where this is supposedly fixed? Which released version of GStreamer contains the fix?
There hasn't been a release yet with the fix, it's only in CVS so far unfortunately. The 'target milestone' field contains the version that will have the fix.
These are the commits:
Of course it is possible that they don't apply to the 0.10.14 release and/or rely on other changes made since the last release.
This bug has also been reported here: