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 604539 - EOS not propagated from dvbsrc
EOS not propagated from dvbsrc
Status: RESOLVED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: gst-plugins-bad
0.10.17
Other Linux
: Normal major
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-12-14 13:49 UTC by Havard Bjerke
Modified: 2011-08-19 04:55 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Havard Bjerke 2009-12-14 13:49:12 UTC
I run a streaming server from DVB-S using dvbbasebin. A few times in a day dvbbasebin stops emitting buffers without any messages on the bus nor emitting any events on any of its src pads. After attaching an event probe on the dvbbasebin's dvbsrc I can see that the dvbsrc emits an EOS event, but it is not propagated to the dvbbasebin's src pad.

I think a better behavior is that dvbbasebin in this case emits an EOS event, rather than silently stopping, but even better is if the stream never stops at all, if possible.
Comment 1 Tim-Philipp Müller 2010-01-08 20:36:56 UTC
> I can see that the dvbsrc emits an EOS event, but it is not
> propagated to the dvbbasebin's src pad.

Any idea where it gets stuck? (you could call gst_debug_get_default_threshold(GST_LEVEL_LOG) to enable the debugging system when you get the EOS event in the probe and then dump that to a file with 2>dbg.log)
Comment 2 Havard Bjerke 2010-01-18 12:35:57 UTC
It's been running continuously for a week, and it hasn't stopped yet. I suspect that the reason why it sometimes stops might be temporary loss of signal. Unfortunately, I don't have physical access to the device, so I can't force a signal loss. What happens with dvbbasebin if the signal is lost temporarily?
Comment 3 Havard Bjerke 2010-01-22 12:53:16 UTC
Finally it stopped, and this is the message that I get:

** (<unknown>:19981): WARNING **: Error setting tone: Connection timed out
Comment 4 Sebastian Dröge (slomo) 2011-05-23 14:26:03 UTC
Please try to get a debug log as explained in comment #1.
Comment 5 Akhil Laddha 2011-07-07 05:23:59 UTC
Havard, were you able to collect debug log as requested ?
Comment 6 Akhil Laddha 2011-08-19 04:55:58 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!