The updated libvpx.so ships 7.0 libs and it seems simply ffmpeg was not updated at the same time…
What happens from time to time on rolling release models
If you do … you could end up like some others on the last hwinfo update overwriting /sbin with an empty folder … which results in real panic for your system.
Same issue, caused by MEGASync because uses ffmpeg3.4 for some reason. Just removed ffmpeg3.4 which will remove MEGASync. Update the system and re-install MEGASync.
I also have this problem, and yes I have Megasync installed.
Should I wait for the problem to be resolved? I would not like to uninstall Megasync and install again.
If you check the comments on the Megasync package’s AUR page, it looks like the issue was resolved 2 days ago. The package no longer requires ffmpeg 3.4.
The ffmpeg3.4 became too problematic with the latest libvpx/x264 update, so I took the liberty to push a fix to build it with ffmpeg. Hope you don’t mind.
For anyone experiencing this problem, the publisher of the AUR package of megasync solved the issue. megasync no longer requires ffmpeg3.4.
So to make a full update of your system, update only the megasync package using your preferred AUR helper, this will remove the dependency on ffmpeg3.4 so you can now remove it without unistalling megasync.
yay -Sy megasync
sudo pacman -Rsn ffmpeg3.4
sudo pacman -Syu