Help debugging blacklisted plugin

[Patrick Doyle]

Thanks for the tip Shawn.

Updating the shared lib links didn't help.

Ultimately I was able to track down the source of the problem to the
fact that one of us installed a custom version of gstreamer in
/usr/local/lib.  Once I cleaned up the debris from that, I was able to
recompile and re-install my plugin and have gst-inspect-1.0 work for
both my plugin and for standard plugins without having to set
LD_LIBRARY_PATH.

Thanks for the help!

--wpd


On Wed, Jul 9, 2014 at 11:09 AM, Shawn Lewis <shlewis at gmail.com> wrote:
> To clear the cache un Ubuntu: "rm -rf ~/.cache/gstreamer-1.0"
>
> You also might just need to run "sudo ldconfig" to update your shared
> lib links for libs that you built and installed in /usr/local/lib. You
> may be able to get rid of the LD_LIBRARY_PATH you specified if that
> works.
>
> You can also specify the gstreamer plugin path manually:
>
> LD_LIBRARY_PATH=/usr/local/lib gst-inspect-1.0
> --gst-plugin-path=/usr/local/lib/gstreamer-1.0 udpsink
>
> --gst-plugin-path works with other gstreamer binaries as well, like
> gst-launch-1.0
>
> On Wed, Jul 9, 2014 at 7:52 AM, Patrick Doyle <wpdster at gmail.com> wrote:
>> Thanks, that's a great tip.
>>
>> $ gst-inspect-1.0 /usr/local/lib/gstreamer-1.0/libgstaravis-0.4.so
>> Could not load plugin file: File
>> "/usr/local/lib/gstreamer-1.0/libgstaravis-0.4.so" appears to be a
>> GStreamer plugin, but it failed to initialize
>>
>> OK, so why did it fail to initialize?  I expect it failed to
>> initialize because it depends on another shared library,
>> libaravis-0.4.so, which lives in /usr/local/lib.  So I tried setting
>> LD_LIBRARY_PATH to point to /usr/local/lib:
>>
>> LD_LIBRARY_PATH=/usr/local/lib gst-inspect-1.0
>> /usr/local/lib/gstreamer-1.0/libgstaravis-0.4.so
>> Plugin Details:
>>   Name: aravissrc
>> …
>>
>> Great!  Errr, except that setting LD_LIBRARY_PATH thusly (somehow)
>> renders it impossible for gstreamer to locate other plugins:
>>
>> LD_LIBRARY_PATH=/usr/local/lib gst-inspect-1.0 udpsink
>> No such element or plugin 'udpsink'
>>
>> I'm so confused!
>>
>> As we have used this particular board for a number of different
>> development efforts, I wonder if some debris from other projects might
>> be leftover in ld or gstreamer cache files.  Is there a way I can
>> clear out such cache files, or am I chasing the wrong red herring
>> there?
>>
>> --wpd
>>
>>
>> On Wed, Jul 9, 2014 at 10:41 AM, Michael Grüner
>> <michael.gruner at ridgerun.com> wrote:
>>> Hi
>>>
>>> You can inspect the library directly. That will likely print out why was the
>>> plugin blacklisted. For example:
>>>
>>> gst-inspect-1.0 /usr/lib/gstreamer-1.0/libmyfailedplugin.so
>>>
>>> Michael
>>>
>>>
>>> -----Original Message-----
>>> From: Patrick Doyle <wpdster at gmail.com>
>>> To: gstreamer-devel <gstreamer-devel at lists.freedesktop.org>
>>> Sent: Wed, 09 Jul 2014 8:20
>>> Subject: Help debugging blacklisted plugin
>>>
>>> Help!
>>>
>>> I'm not even sure what I don't know yet, but I compiled and installed
>>> a plugin on a Ubuntu based ARM host, but that plugin is blacklisted.
>>> This works fine on my Ubuntu based x86 host.
>>>
>>> How can I figure out why gst-inspect-1.0 -b reports my plugin as
>>> blacklisted?
>>>
>>> --wpd
>>> _______________________________________________
>>> gstreamer-devel mailing list
>>> gstreamer-devel at lists.freedesktop.org
>>> http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
>>>
>>> _______________________________________________
>>> gstreamer-devel mailing list
>>> gstreamer-devel at lists.freedesktop.org
>>> http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
>>>
>> _______________________________________________
>> gstreamer-devel mailing list
>> gstreamer-devel at lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
> _______________________________________________
> gstreamer-devel mailing list
> gstreamer-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel