** Description changed: - [Impact] + [Impact] OpenJFX's media and webkit native libraries are missing from amd64 builds in Focal and Groovy. This is a regression from Bionic. This prevents applications that depend on these libraries from working correctly. [Test Case] The libjfxmedia.so and libjfxwebkit.so should be present in the libopenjfx-jni binary for all archs. One can see in the amd64 package listing for Focal [1,2] and Groovy [3,4] that libjfxmedia.so and libjfxwebkit.so are only available on arm64, armhf, ppc64el, and s390x. [1] https://packages.ubuntu.com/search?searchon=contents&keywords=libjfxmedia.so&mode=exactfilename&suite=focal&arch=any [2] https://packages.ubuntu.com/search?searchon=contents&keywords=libjfxwebkit.so&mode=exactfilename&suite=focal&arch=any [3] https://packages.ubuntu.com/search?searchon=contents&keywords=libjfxmedia.so&mode=exactfilename&suite=groovy&arch=any [4] https://packages.ubuntu.com/search?searchon=contents&keywords=libjfxwebkit.so&mode=exactfilename&suite=groovy&arch=any - Another possible test case is running pdfsam in the console to split a PDF file (after pdfsam bug 1887142 is fixed) and look if errors as: Caused by: java.lang.UnsatisfiedLinkError: no jfxmedia in java.library.path: [/usr/java/packages/lib, /usr/lib/x86_64-linux-gnu/jni, /lib/x86_64-linux-gnu, /usr/lib/x86_64-linux-gnu, /usr/lib/jni, /lib, /usr/lib] show up in the stdout. A sound should be played if everything works. - - [Regression Potential] + [Regression Potential] Enabling the native libraries will allow applications to use them again. - * This can trigger errors in applications that were not detected while the libraries were missing. + * This can trigger errors in applications that hidden by the fact that there were no native libraries to use. * This can cause applications that use OpenJFX to fail to run or crash during runtime. - It is unlikely that autopkgtest will detect such errors given that OpenJFX _did_ migrate when the native libraries were missing (and should have caused errors). + It is unlikely that autopkgtest will detect such errors given that OpenJFX _did_ migrate when the native libraries were missing (and that should have caused errors). [Other Info] - [Original Report] I'm trying to run BlueJ on Ubuntu 20.04 (fresh install), while the main app runs the editor refuses to start, looking at its logs apparently it can't find jfxwebkit. So I tried to search for it, and apparently it is present in the other architectures for Focal as well as all architectures in Eoan, Bionic and Xenial in the libopenjfx-jni package, but not for Focal amd64. The version of openjfx I have is 11.0.7+0-2ubuntu1. I have also attached BlueJ's log for reference.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877000 Title: openjfx is missing native libraries for webkit and media To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjfx/+bug/1877000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
