https://bugs.kde.org/show_bug.cgi?id=109060
--- Comment #30 from caulier.gil...@gmail.com --- If i remove libaom.so.0 from the bundle, of course it crash: [gilles@localhost pipo]$ ./AppRun -- digiKam Linux AppImage Bundle -- Use 'help' as CLI argument to know all available options for digiKam application. -- Notes: to integrate this bundle to your desktop, use AppImageLauncher. -- to enable all debug messages on the console, use 'export QT_LOGGING_RULES="digikam*=true"'. Check library libudev.so.0 Check library libxcb-dri3.so.0 Check library libcrypto.so.1.1 Check library libssl.so.1.1 Check library libnss3.so Check library libnssutil3.so Check library libsmime3.so -- Preloading shared libs: :/usr/lib64/libxcb-dri3.so.0:/usr/lib64/libcrypto.so.1.1:/usr/lib64/libssl.so.1.1:/usr/lib64/libnss3.so:/usr/lib64/libnssutil3.so:/usr/lib64/libsmime3.so digikam: error while loading shared libraries: libaom.so.0: cannot open shared object file: No such file or directory ... but if i create a symlink like this : ln -s libaom.so.3 libaom.so.0 digiKam starts and export to AVIF work as expected from Image Editor !!! So if a guru can explain to me why the loader is not able to mix different versions of a library at run-time, well i can offer a beer, because this combination is technically possible. Or perhaps it's a limitation of AppImage, i don't know... Gilles -- You are receiving this mail because: You are watching all bug changes.
