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 110589 - [0.6.1] bins never signal EOS
[0.6.1] bins never signal EOS
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
0.6.0
Other Linux
: Normal normal
: 0.6.x
Assigned To: GStreamer Maintainers
GStreamer Maintainers
: 104839 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2003-04-11 22:20 UTC by Benjamin Otte (Company)
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
see above (972 bytes, patch)
2003-04-11 22:21 UTC, Benjamin Otte (Company)
none Details | Review

Description Benjamin Otte (Company) 2003-04-11 22:20:46 UTC
This was actually a Rhythmbox issue, because Rhythmbox connected to the
sink and waited for the EOS on the sink.
Since using GConf keys however, the "sink" element is a bin and bins don't
signal EOS.

I believe the correct behaviour would be for a bin to signal EOS when all
elements inside the bin sent EOS.
An alternative would be to remove the EOS signal from bins (how?) or at all.

The attached patch implements EOS on bins in a quick and dirty way.


I'd like some core guy to comment on it, before I commit this to HEAD.
Comment 1 Benjamin Otte (Company) 2003-04-11 22:21:28 UTC
Created attachment 15655 [details] [review]
see above
Comment 2 Wim Taymans 2003-04-11 22:29:28 UTC
yes, quick and dirty but very acceptable for now. commit to HEAD (and
possibly 0.6.1) 
Comment 3 Ronald Bultje 2003-04-12 13:13:38 UTC
Will do - marking... I'll make a new 0.6.1 patchlist in a few hours.
Comment 4 Benjamin Otte (Company) 2003-04-12 13:40:50 UTC
applied to HEAD
Comment 5 Ronald Bultje 2003-04-13 11:26:26 UTC
This one is in 0.6.1 - closing.
Comment 6 Benjamin Otte (Company) 2003-05-14 15:12:05 UTC
*** Bug 104839 has been marked as a duplicate of this bug. ***