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 579046 - Internal GStreamer error: clock problem
Internal GStreamer error: clock problem
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: dont know
0.10.x
Other Linux
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-04-15 13:32 UTC by Fabien LOUIS
Modified: 2010-09-23 12:59 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Debugs logs (366.24 KB, application/zip)
2009-04-17 10:38 UTC, Fabien LOUIS
Details

Description Fabien LOUIS 2009-04-15 13:32:53 UTC
When I call RequestStream on a Telepathy StreamedMedia channel, I get:

0:00:41.128895500  8202  0x9bba760 INFO              GST_PADS gstpad.c:3235:gst_pad_event_default_dispatch:<send_rtp_tee_1:src1> Sending event 0x9e968a0 (latency) to all internally linked pads
0:00:41.140193741  8202  0x9bba760 INFO              GST_PADS gstpad.c:3235:gst_pad_event_default_dispatch:<rtpsession0:send_rtp_src> Sending event 0x9e968a0 (latency) to all internally linked pads
0:00:41.140245821  8202  0x9bba760 WARN              GST_PADS gstpad.c:3005:gst_pad_iterate_internal_links_default:<rtpsession0:send_rtp_src> Making unsafe iterator
0:00:41.140320821  8202  0x9bba760 WARN                   bin gstbin.c:2237:gst_bin_do_latency_func:<bin1> failed to configure latency of 0:00:00.000000000
0:00:41.140356381  8202  0x9bba760 WARN                   bin gstbin.c:2240:gst_bin_do_latency_func:<bin1> warning: Failed to configure latency of 0:00:00.000000000
0:00:41.140494341  8202  0x9bba760 INFO      GST_ERROR_SYSTEM gstelement.c:1675:gst_element_message_full:<bin1> posting message: Internal GStreamer error: clock problem.  Please file a bug at http://bugzilla.gnome.org/enter_bug.cgi?product=GStreamer.
0:00:41.140564461  8202  0x9bba760 INFO      GST_ERROR_SYSTEM gstelement.c:1698:gst_element_message_full:<bin1> posted warning message: Internal GStreamer error: clock problem.  Please file a bug at http://bugzilla.gnome.org/enter_bug.cgi?product=GStreamer.
0:00:41.140659701  8202  0x9bba760 INFO            GST_STATES gstelement.c:2150:gst_element_continue_state:<fakesink3> completed state change to PLAYING
0:00:41.140689461  8202  0x9bba760 INFO            GST_STATES gstelement.c:2163:gst_element_continue_state:<fakesink3> posting state-changed PAUSED to PLAYING
0:00:41.140736501  8202  0x9bba760 INFO            GST_STATES gstbin.c:2355:gst_bin_change_state_func:<bin1> child 'fakesink3' changed state to 4(PLAYING) successfully
Comment 1 Wim Taymans 2009-04-17 09:29:33 UTC
Some element is not accepting the LATENCY event, can you attach a compressed debug log like this:

GST_DEBUG=*PAD*:5,*bin*:5 <your_application> >debug.log 2>&1

Comment 2 Fabien LOUIS 2009-04-17 10:38:06 UTC
Created attachment 132816 [details]
Debugs logs

These are the files (Two files because I use two clients who try to make a call)
Comment 3 Wim Taymans 2009-04-17 10:53:45 UTC
This is fixed in -bad 0.10.9. What version are you using?
Comment 4 Fabien LOUIS 2009-04-17 12:37:05 UTC
I have Ubuntu Jaunty with gstreamer0.10-plugins-bad (0.10.11-2ubuntu1)
Comment 5 Tim-Philipp Müller 2010-09-23 12:59:34 UTC
This is quite old, I think there have been a bunch of fixes in various places. There were problems with rtpmux for example, iirc. I'm just going to close this as obsolete for now since I think we'd know if these problems still existed.

But if this still is a problem with current versions of things (as per GStreamer PPA), please do re-open this bug.