On 01/06/2019 06:00 PM, George from the tribe wrote:
I haven't tried going back to 5.2, might try that if I have to. Here is the output:
# ls -al /usr/lib64/libvpx.so* lrwxrwxrwx 1 root root 15 Jan 27 2018 /usr/lib64/libvpx.so.1 -> libvpx.so.1.3.0 lrwxrwxrwx 1 root root 15 Jan 27 2018 /usr/lib64/libvpx.so.1.3 -> libvpx.so.1.3.0 -rwxr-xr-x 1 root root 1678328 Jan 23 2018 /usr/lib64/libvpx.so.1.3.0 lrwxrwxrwx 1 root root 15 Jul 14 22:17 /usr/lib64/libvpx.so.5 -> libvpx.so.5.0.0 lrwxrwxrwx 1 root root 15 Jul 14 22:17 /usr/lib64/libvpx.so.5.0 -> libvpx.so.5.0.0 -rwxr-xr-x 1 root root 2321088 Jun 8 2018 /usr/lib64/libvpx.so.5.0.0
That's what I have on Leap, on Arch, only libvpx.so.5 is present. I wonder if Virtualbox 6 is picking up the wrong libvpx (or there is a dependency issue triggered with the Oracle build?) I always use the Oracle builds and up through 5.2.22 on Leap there have been no issues. When arch jumped from 4.19 to 4.20 5.2.22 would fail which is what prompted me to move to Virtualbox 6 there. Personally, unless you need some feature that 6 provides, I would wait a minor-version cycle before moving to 6 if you have the option. There may still be a few unexpected "features" that need fixing in 6 (my bet is there is a memory leak somewhere...) -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org