-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
error while loading shared libraries: libmakemkv.so.1: cannot open shared object file: No such file or directory #51
Comments
I faced a similar issue and decided to build it from the source and binary tars to get around it. Something to look into is it should be possible to create another flatpak requiring this one as a dependency and setting Just a caveat that I haven't authored any flatpaks myself and stumbled across this after doing some light googling |
@NeuroticTumbleweed Do you have a guide handy? This link from the MakeMKV forums is 404ing on the source and binaries download in the first step. |
I found a PPA for Apt that worked neatly with
This requires a registration key. From there It definitely would be great to have the missing dependency included in the Flatpak, however. |
Confirmed this is also a problem since upgrading to Fedora 40 - it worked on Fedora 39. The "missing" library does exist though, so I'm not sure what's wrong. I've never used a flatpak before.
|
error while loading shared libraries: libmakemkv.so.1: cannot open shared object file: No such file or directory
This error occurs when i try to run sdftool or makemkvcon from /var/lib/flatpak/app/com.makemkv.MakeMKV/current/f3608af10eb2297e03057c78cf7bb20b55ce00996b2a042b6097a30574e639d5/files/bin I have been having major issues trying to build makemkv for my distro and installed flatpak instead. I want to get libredrive working but since i have no avenues to use the flash tool to do that im kinda stuck and would really appreciate some help or a fix if this is truely a bug and not my own linux incompetence.
The text was updated successfully, but these errors were encountered: