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 619041 - Seek fails, and subsequent query_position calls fail
Seek fails, and subsequent query_position calls fail
Status: RESOLVED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: dont know
0.10.28
Other Linux
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-05-18 22:56 UTC by Gabriel Burt
Modified: 2012-09-29 12:41 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
GST_DEBUG=2 log (883 bytes, text/plain)
2010-05-18 22:56 UTC, Gabriel Burt 		Details
GST_DEBUG=3 log (7.55 KB, text/plain)
2010-05-18 22:56 UTC, Gabriel Burt 		Details

Description Gabriel Burt 2010-05-18 22:56:17 UTC 
Created attachment 161391 [details]
GST_DEBUG=2 log

On each transition, I'm setting a new URI, and then issuing a seek to a given position (a bookmarked position).  Usually this works OK, but about 1 in 10 times it fails to seek, starting playback of the new URI from the beginning.  And subsequent query_position calls fail.

I'm attaching two logs, one with GST_DEBUG=2 where you can see a WARN from id3demux2 saying "Downstream did not handle newsegment event as it should" etc, and the query_position fails.

The other is with GST_DEBUG=3, but at this debug level I can't reproduce the full problem - the app freezes, with the main loop stuck trying to do the seek.
Comment 1 Gabriel Burt 2010-05-18 22:56:44 UTC 
Created attachment 161392 [details]
GST_DEBUG=3 log
Comment 2 Tim-Philipp Müller 2012-02-18 16:32:48 UTC 
Sorry, what's the context here? On each transition? What transition?
Comment 3 Akhil Laddha 2012-06-18 16:38:19 UTC 
Gabriel, ping, can you please provide more information ?
Comment 4 Tim-Philipp Müller 2012-09-29 12:41:16 UTC 
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!