libtracker-miner-3.0.so: cannot open shared object file: No such file or directory
tracker-miners: 3.1.2 on Arch Linux
While trying to launch tracker with tracker daemon --start
or indirectly triggering miners (e.g. by launching gnome-photos) I see the following error messages in my system journal:
- Aug 11 22:58:10 systemd[949]: Starting Tracker Filesystem Indexing Proxy...
- Aug 11 22:58:10 tracker-miner-fs-control-3[21896]: /usr/lib/tracker-miner-fs-control-3: error while loading shared libraries: libtracker-miner-3.0.so: cannot open shared object file: No such file or directory
- Aug 11 22:58:10 systemd[949]: tracker-miner-fs-control-3.service: Main process exited, code=exited, status=127/n/a
- Aug 11 22:58:10 systemd[949]: tracker-miner-fs-control-3.service: Failed with result 'exit-code'.
- Aug 11 22:58:10 systemd[949]: Failed to start Tracker Filesystem Indexing Proxy.
or
- Aug 11 22:16:49 Starting Tracker RSS/ATOM feed data miner...
- Aug 11 22:16:49 tracker-miner-rss-3[18679]: /usr/lib/tracker-miner-rss-3: error while loading shared libraries: libtracker-miner-3.0.so: cannot open shared object file: No such file or directory
- Aug 11 22:16:49 systemd[949]: tracker-miner-rss-3.service: Main process exited, code=exited, status=127/n/a
- Aug 11 22:16:49 systemd[949]: tracker-miner-rss-3.service: Failed with result 'exit-code'.
- Aug 11 22:16:49 systemd[949]: Failed to start Tracker RSS/ATOM feed data miner.
Launching those binaries manually generates the same error message.
ldd output for /usr/lib/tracker-miner-fs-control-3
linux-vdso.so.1 (0x00007ffe9acde000)
libtracker-miner-3.0.so => not found
libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0x00007ff6d9504000)
libgio-2.0.so.0 => /usr/lib/libgio-2.0.so.0 (0x00007ff6d9347000)
libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0x00007ff6d92ed000)
libc.so.6 => /usr/lib/libc.so.6 (0x00007ff6d9121000)
libpcre.so.1 => /usr/lib/libpcre.so.1 (0x00007ff6d90aa000)
libpthread.so.0 => /usr/lib/libpthread.so.0 (0x00007ff6d9087000)
libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0x00007ff6d9082000)
libz.so.1 => /usr/lib/libz.so.1 (0x00007ff6d9068000)
libmount.so.1 => /usr/lib/libmount.so.1 (0x00007ff6d9008000)
libresolv.so.2 => /usr/lib/libresolv.so.2 (0x00007ff6d8fee000)
libffi.so.7 => /usr/lib/libffi.so.7 (0x00007ff6d8fe2000)
/lib64/ld-linux-x86-64.so.2 => /usr/lib64/ld-linux-x86-64.so.2 (0x00007ff6d9674000)
libdl.so.2 => /usr/lib/libdl.so.2 (0x00007ff6d8fd9000)
libblkid.so.1 => /usr/lib/libblkid.so.1 (0x00007ff6d8f83000)
librt.so.1 => /usr/lib/librt.so.1 (0x00007ff6d8f78000)
Further investigation shows that libtracker-miner-3.0.so gets installed to /usr/lib/tracker-miners-3.0/ and is therefore not found by the dynamic linker. A ld.so.conf file which allows the linker to discover this directory seems to be missing. Creating a symlink in /usr/lib/ which points to /usr/lib/tracker-miners-3.0/libtracker-miner-3.0.so also resolves this issue.
Edited by Jan Sonntag