After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 466717 - gst_event_new_new_segment_full:assertion `start <= stop' failed
gst_event_new_new_segment_full:assertion `start <= stop' failed
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gst-plugins-base
0.10.3
Other Linux
: Normal critical
: 0.10.15
Assigned To: Wim Taymans
GStreamer Maintainers
Depends on:
Blocks: 466352
 
 
Reported: 2007-08-14 18:42 UTC by Andreas Røsdal
Modified: 2007-10-31 18:36 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
debug output (531.79 KB, text/plain)
2007-08-16 16:08 UTC, Andreas Røsdal
Details

Description Andreas Røsdal 2007-08-14 18:42:36 UTC
There is a new problem with playing sounds in gnome-games, using GStreamer
0.10.3. 

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:

GStreamer 0.10.13
gnome-games 2.19.90
GNOME 2.19.6

The code is here:

http://svn.gnome.org/viewcvs/gnome-games/trunk/libgames-support/games-sound.c?view=markup

Sound is played successfully the first time, then the next sounds are not
played correctly. This did not happen in previous versions of GStreamer.
Comment 1 Wim Taymans 2007-08-16 15:51:54 UTC
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.
Comment 2 Andreas Røsdal 2007-08-16 16:08:03 UTC
Created attachment 93785 [details]
debug output

Thanks for the interest in helping. The debug information is attached,
for when playing several seconds of gnometris.
Comment 3 Wim Taymans 2007-08-21 10:40:08 UTC
It looks like oggdemux cannot deal with the very small ogg files.
Comment 4 Wim Taymans 2007-08-21 12:08:16 UTC
        * 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. 
        Fixes #466717.

        * ext/ogg/gstoggdemux.c: (gst_ogg_demux_read_chain),
        (gst_ogg_demux_collect_chain_info):
        Also submit the eos page when trying to find the first timestamp.
        See #466717.
Comment 5 Andreas Røsdal 2007-08-21 17:01:21 UTC
Thanks :)
Comment 6 Andreas Røsdal 2007-08-21 17:08:07 UTC
Did you commit the changes to gstoggmux.c?  I can't see them on webcvs...
Comment 7 Andreas Røsdal 2007-08-21 17:09:18 UTC
OOops... I found it now. Thanks again. 
Comment 8 Andreas Røsdal 2007-10-01 19:37:20 UTC
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?
Comment 9 Tim-Philipp Müller 2007-10-01 20:32:25 UTC
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.
Comment 10 Tim-Philipp Müller 2007-10-04 18:41:05 UTC
These are the commits:

http://webcvs.freedesktop.org/gstreamer/gst-plugins-base/ext/vorbis/vorbisdec.c?r1=1.127&r2=1.128
http://webcvs.freedesktop.org/gstreamer/gst-plugins-base/ext/ogg/gstoggdemux.c?r1=1.180&r2=1.181

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.  
Comment 11 Andreas Røsdal 2007-10-31 18:36:07 UTC
This bug has also been reported here:

https://bugs.launchpad.net/ubuntu/+source/gnome-games/+bug/159063

Arrrghh.