Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#44729 - [mpv] Latest libvpx update breaks mpv 0.8.3-1
Attached to Project:
Community Packages
Opened by Yann.O (Yann.O) - Saturday, 25 April 2015, 15:08 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 25 April 2015, 15:20 GMT
Opened by Yann.O (Yann.O) - Saturday, 25 April 2015, 15:08 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 25 April 2015, 15:20 GMT
|
DetailsDescription:
Shared library change Additional info: Last libvpx update changed the name of the library file mpv is linked against. After performing the update, mpv would not start, outputting: > mpv mpv: error while loading shared libraries: libvpx.so.1: cannot open shared object file: No such file or directory Ugly fix : > sudo ln -s /usr/lib/libvpx.so.2.0.0 /usr/lib/libvpx.so.1 Proper would be to compile mpv against the new libvpx version. Affected : * mpv 0.8.3-1 * libvpx 1.4.0-2 Steps to reproduce: Update libvpx to the latest version, try to run mpv. |
This task depends upon
Comment by Doug Newgard (Scimmia) -
Saturday, 25 April 2015, 15:19 GMT
Nope. mpv is not linked to libvpx at all. ldd is misleading because it's recursive. Most likely your system is not up to date or you have something from the AUR that mpv is linked to that is then linked to libvpx. If you don't know what it is, lddtree from pax-utils can help you find it.