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 317341 - after linking ghost pads, one target pad does not have a peer
after linking ghost pads, one target pad does not have a peer
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
git master
Other Linux
: Normal major
: 0.9.5
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-09-27 14:29 UTC by Josef Zlomek
Modified: 2005-11-09 22:02 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Testcase for linking ghost pads (1.31 KB, text/plain)
2005-09-27 14:31 UTC, Josef Zlomek 		Details

Description Josef Zlomek 2005-09-27 14:29:31 UTC 
I create 2 bins, each with some elements, and create ghost pads for the bins.
When I link the ghost pads, they have peers, but one of their target pads does
not have a peer.

For example, when I have a filesrc in one bin and avidemux in the beginning of
the other bin, the avidemux sink pad does not have a peer and can't find out
that the source element supports seeking, and finally fails to change state to
PAUSED.

See the testcase, with fakesrc and fakesink in separate bins.
Comment 1 Josef Zlomek 2005-09-27 14:31:55 UTC 
Created attachment 52727 [details]
Testcase for linking ghost pads
Comment 2 Wim Taymans 2005-11-09 19:02:11 UTC 
testcase added in check, fixed in CVS.