Created attachment 406717 [details] strace of libextractor-extract run (showing plugin load attempts at bad paths) Description of problem: On my x86_64 Fedora 12 system, I noticed that both libextractor-extract and doodle failed to extract any metadata from any file I tested with, including explicitly supported filetypes. An strace (attached) on libextractor-extract showed that it was looking in several locations, none of them correct, for its plugins. Without any plugins loaded, libextractor does precisely nothing. (The first location attempted is, tellingly, /usr/lib/libextractor/ -- rather than the /usr/lib64/libextractor/ path that actually contains the plugins. Compile-time error in defining the plugin path, looks like?) Version-Release number of selected component (if applicable): libextractor-0.5.23-0.fc12.x86_64 libextractor-plugins-base-0.5.23-0.fc12.x86_64 libextractor-plugins-exiv2-0.5.23-0.fc12.x86_64 libextractor-plugins-flac-0.5.23-0.fc12.x86_64 libextractor-plugins-ogg-0.5.23-0.fc12.x86_64 libextractor-plugins-ole2-0.5.23-0.fc12.x86_64 libextractor-plugins-pdf-0.5.23-0.fc12.x86_64 libextractor-plugins-rpm-0.5.23-0.fc12.x86_64 libextractor-plugins-thumbnailgtk-0.5.23-0.fc12.x86_64 How reproducible: 100% of the time, by running libextractor-extract on an x86_64 Fedora 12 system. Steps to Reproduce: 1. Install libextractor and at least libextractor-plugins-base from rpm 2. Find a file of supported filetype (e.g. FILE=somefile.pdf, with libextractor-plugins-pdf installed) 3. run: 'libextractor-extract $FILE' Actual results: <nothing> Expected results: (At least...) % libextractor-extract $FILE format - PDF 1.2 mimetype - application/pdf Additional info: Further testing revealed that manually executing 'ldconfig /usr/lib64/libextractor/' as root caused libextractor-extract to begin functioning. So, a hackish workaround may be the addition of a config file to /etc/ld.so.conf.d/ that adds this path to ldconfig's cache.
Of course, only AFTER reporting this do I find the libextractor builds in updates-testing, which refer to bug 452504 -- a report of the same problem. (Grrr. I KNOW I searched, I thought extensively, for previous reports before I filed this.) Anyway, closing as a dup of #452504. *** This bug has been marked as a duplicate of bug 452504 ***