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 712318 - Tells Totem the stream is seekable
Tells Totem the stream is seekable
Status: RESOLVED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: dont know
1.2.1
Other Linux
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-11-14 17:04 UTC by Bastien Nocera
Modified: 2015-02-24 15:42 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Bastien Nocera 2013-11-14 17:04:45 UTC
We have a private stream for meetings at RH, where the server is sometimes quite temperamental. The server disconnects/EOS's. When that happens and repeat is on, Totem will either close and re-open the stream (not seekable), or seek back and start playing again (seekable). GStreamer is telling Totem that the stream is seekable though, and we end up with "Can't seek to beginning, not seekable" instead of closing/reopening and playback starting again automatically.
Comment 1 Bastien Nocera 2013-11-14 17:05:17 UTC
This is using 1.2.1 on Fedora 20.
Comment 2 Olivier Crête 2013-11-29 01:39:26 UTC
I guess you have to debug this with Wim. I assume you're using icecast? Not much we can do without some more information though
Comment 3 Tim-Philipp Müller 2015-02-24 12:48:42 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment.
Thanks!
Comment 4 Bastien Nocera 2015-02-24 15:07:21 UTC
This is the script that's used for streaming:
http://people.freedesktop.org/~halfline/start-stream-1.0
Comment 5 Tim-Philipp Müller 2015-02-24 15:32:56 UTC
Thanks Bastien. I don't think that helps much though, since this script just captures + sends the stream to the actual streaming server, and Totem presumably connects to the streaming server.

Perhaps you could set up or link to a test stream that reproduces the issue? (Wim should be able to connect to internal resources)

A GST_DEBUG=*:6 log (when running Totem) would also help probably.
Comment 6 Tim-Philipp Müller 2015-02-24 15:34:01 UTC
Also, have you checked if this still happens with 1.4.x or git master?
Comment 7 Bastien Nocera 2015-02-24 15:42:15 UTC
The machine has since been taken out of commission it seems. Never mind.