FS#66796 - [ffmpeg] libaom.so.0 - out of date?

Attached to Project: Arch Linux
Opened by James (thx1138) - Wednesday, 27 May 2020, 03:41 GMT
Last edited by Maxime Gauduin (Alucryd) - Tuesday, 21 July 2020, 12:11 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Maxime Gauduin (Alucryd)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No


ffmpeg 1:4.2.3-1
aom 2.0.0-1

$ ffmpeg
ffmpeg: error while loading shared libraries: libaom.so.0: cannot open shared object file: No such file or directory

$ pacman -Ql aom | grep libaom
aom /usr/lib/libaom.so
aom /usr/lib/libaom.so.2
aom /usr/lib/libaom.so.2.0.0

$ pacman -Qi aom
Build Date : Wed 20 May 2020 07:52:05 AM MDT

This task depends upon

Closed by  Maxime Gauduin (Alucryd)
Tuesday, 21 July 2020, 12:11 GMT
Reason for closing:  Works for me
Comment by Jan de Groot (JGC) - Wednesday, 27 May 2020, 08:05 GMT
You're using gnome-unstable. Bumping aom needs some rebuilds, but focus is not on soname rebuilds in gnome-unstable atm.
Comment by Scott Mumford (wilberfan) - Thursday, 02 July 2020, 00:51 GMT
I have to keep my mediaserver on aom-1.0.0-, otherwise it breaks emby-server playback. Firefox won't play Twitter and Instagram without aom-2.0.0-1. Using gnome (v3.36.3) and XFCE4.