So basically I am trying to make omxplayer work on my raspberry PI 2 model B running on fedora arm 23, I downloaded the last .deb package for omx player and unpacked it and am actually trying to get the shared libraries necessary to run it.

Here are some outputs explaining further what s going on :

#ldd omxplayer.bin | grep "not found"
    libavutil.so.55 => not found
    libavcodec.so.57 => not found
    libavformat.so.57 => not found
    libswresample.so.2 => not found
    libpcre.so.3 => not found

I tried #dnf provides "*/libavutil.so.55" in order to know what package to download but I didn't get any. Error: No Matches found Any ideas on how to get these shared librarys otherwise?

Here is more information on what I am trying to do link

So after doing export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib64:/usr/lib/omxplay‌​er I got some of those librarys and the output of #ldd omxplayer.bin | grep "not found" became

    libpcre.so.3 => not found
    libssl.so.1.0.0 => not found
    libcrypto.so.1.0.0 => not found

Someone suggested I do #dnf install openssl-devel but I already had it

`Package openssl-devel-1:1.0.2h-3.fc23.armv7hl is already installed,skipping.Dependencies resolved. Nothing to do. Complete!` 

#ls /lib |grep libssl gives the following


libavutil.so.55 is provided by the ffmpeg-libs from rpmfusion:

$ dnf provides "*/libavutil.so*"
ffmpeg-libs-3.0.2-4.fc24.x86_64 : Libraries for ffmpeg
Repo        : rpmfusion-free-updates
$ rpm -ql ffmpeg-libs | grep libavutil

You probably don't have this repository installed:


  • Correct answer but @Ezwig Don't use those because the Fedora repo ones won't exploit the pi hardware (and may not work at all); in this case that's a library that's part of the bunch included with omxplayer. Copy the usr/lib/omxplayer player directory into /usr/lib and run ldconfig. – goldilocks Aug 29 '16 at 12:35
  • ou. I read you are using F24 (where I searched for these files). So the problem will probably be that you installed Debian package into Fedora. – Jakuje Aug 29 '16 at 12:35
  • Ah -- there was a critical step missing from that answer WRT to adding the directories to the linker cache for ldconfig. I will edit that in... – goldilocks Aug 29 '16 at 12:37
  • @goldilocks in this context, it makes sense. Though it is not the most standard way of doing things on OS level :) – Jakuje Aug 29 '16 at 12:38
  • 1
    NO NO NO NO DO NOT ADD TO LD_LIBRARY_PATH!!! This is not what it is for and doing this except for a temporary test will come back to haunt you, I promise. You need to add the path to the linker cache via a file in /etc/ld.so.conf.d (see that long answer). – goldilocks Aug 29 '16 at 13:47

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.