continued on bug report #11244: i have a fedora 7 running on a x86 vmware virtual machine with virtual network interface 192.168.8.140. I tested telepathy voice call function with a gtalk client on windows machine and a telepathy client on Gentoo Linux. when the fedora telepathy client acts as the caller to initiate a call,the stream engine will fail an assertion and abort. when the fedora telepathy client acts as the callee to receive a call,the stream engine will run,but there's no any sound on both sides of the call. attached is the log file,as wireshark log is binary,so i have to attach a binary tar.bz2 file to you. 1. telepathy-stream-engine.fedora.caller.log stream engine log file when fedora telepathy client acts as a caller 2. telepathy-stream-engine.fedora.callee.log stream engine log file when fedora telepathy client acts as a callee 3. wireshark.fedora.callee.log wireshark capture when fedora telepathy client ascts as a callee
Created attachment 10282 [details] stream engine log
Created attachment 10283 [details] telepathy stream engine log file when fedora telepathy client acts as a caller
Created attachment 10284 [details] telepathy stream engine log file when fedora telepathy client acts as a callee
Created attachment 10285 [details] wireshark capture when fedora telepathy client acts as a callee
Created attachment 10286 [details] telepathy stream engine log file when fedora telepathy client acts as a caller
I believe this may have been fixed in gst-plugins-farsight 0.12.2. Does this still happen with gst-plugins-farsight 0.12.2, farsight 0.1.21, gstreamer 0.10.13, gst-plugins-base 0.10.13 and gst-plugins-good 0.10.6? (Please don't file one bug per platform if the software versions are basically the same and so is the failure mode...)
Bugzilla Upgrade Mass Bug Change NEEDSINFO state was removed in Bugzilla 3.x, reopening any bugs previously listed as NEEDSINFO. - benjsc fd.o Wrangler
Assuming this is fixed since reporter is not forthcoming.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.