Yes, this is very likely going to be true for all future releases unless the build environment is downgraded, or whatever is generating code in the appimage which uses symbols from a libstdc++ release later than the one in Debian 11 et. al. stops doing that (and both those things are most probably Backward Steps in the Overall Scheme Of Things).
It’s not a “bug” in kdenlive introduced by the kdenlive developers, or likely one they can “fix” in kdenlive - it’s an artifact of building the appimage with a newer toolchain.
What is the problem with updating to Debian 12 if you want to use the newest releases of kdenlive? Debian 12 became the current stable release ~5 months ago now, and any regressions with updating to it should be reported to the package(s) concerned there …
Hi ludo, I’ve installed the flatpak version 23.08.3 in a VM with LMDE5 and it works but…but…why should I have to install 3GB or more of stuff in flatpak version when the AppImage is only 206MB?? Strange things and strange world! Also, I’m little bit confused: I don’t understand, but shouldn’t the libraries be implemented in the AppImage regardless of the distribution or version used? This should be the goal of the AppImage packaging, or I think wrong??
The appimage only bundles the “application libraries” - roughly speaking, the things which if you installed a distro packaged version would be dependencies on additional optional packages. It still uses the low level system libraries and kernel from the base system it is running on. It’s not a self-contained bootable image.
In the case of the 23.08.3 appimage, the kdenlive binary in the appimage is linked to the following system libraries not shipped by the appimage: