Bug#699049: libfarstream-0.1-0: seems farstream not detecting audiocodecs

[Vladimir Berezenko]

В сообщении от 29 января 2013 13:51:04 автор Simon McVittie написал:
> >>> on powerpc seems that farstream is not seing any audiocodecs.
> >> 
> >> This is likely to be caused by <http://bugs.debian.org/674156>, for
> >> which powerpc is one of the affected architectures. Please try upgrading
> >> to libgstreamer0.10-0 (>= 0.10.36-1.1) from unstable - that version
> >> should be available on powerpc now (or within a couple of days if your
> >> Debian mirror is slow).
> > 
> > Seems that not helped. After regeneration of codecs.audio.powerpc.cache
> > stayed of the same size - 12 bytes. There's no any MIME types listed
> > there. Of course, i've rebooted after installing 0.10.36-1.1 from
> > unstable.
> 
> Farstream and Gst experts: any ideas?
> 
> Vladimir, if you run "gst-inspect-0.10 speexenc", "gst-inspect-0.10
> rtpspeexpay" on your powerpc, what do you get? Any warning messages? (If
> everything is working, you should get some details of the plugins,
> resembling <http://paste.debian.net/229996/>.)

There were one about opencv, but I think it is not worth to mention.

> If you run a Farstream application from a gnome-terminal or something,
> do you get any warnings from that?

No messages at all.

> Does ~/.gstreamer-0.10/registry.*.bin list details of elements like
> speexenc and rtpspeexpay in its binary data? If you remove both
> codecs.audio.powerpc.cache and ~/.gstreamer-0.10/registry.*.bin,
> then re-run a Farstream application, does that help?

And that step finally helped. Removing all gstreamer and farsight caches and 
regenerating them totally fixed the problem.