To my great surprise, older AppImage versions (22.x, 21.x or 20.x) of Kdenlive cannot be opened, it simply stops in the startup process. This is on my current Manjaro Linux. The current versions work of course, is that normal?
However, Debian has no problems with this.
I thought the AppImages contain everything the program needs to run. Was I wrong about that?
To my surprise, kdenlive-20.08.1-x86_64.appimage can be opened… maybe try again, I can do them all back to 18x -
18.x starting to look ugly.
You can get it here - the KDE store.
Unfortunately, not always.
Hello @Ben
I can do them all back to 18x
Screenshot_20241026_210717` Very surprising for me. On which distro does it work for you? As I said, it doesn’t work on Manjaro, but it works on Debian without any problems.
Hello @Teo
Unfortunately, not always.
That’s a pity, but it’s good that you can live with the fact that not everything is really integrated in the AppImage.
At the end of the day the developer has to draw the line somewhere to not have to include a whole os in the appimmage. So he assumes some very basic stuff is already present on the user system. And most of the developers test only on Ubuntu and fedora. So linux being linux, 90% of the cases the core libraries are the same. But in rare cases they differ between debian and arch (Manjaro).
The flatpak / snap concept is different, they do indeed include “runtimes” that are more or less whole oses.
That is why the same app from the repo can be 7 MB, from appimage 70 MB, from flatpak between 7 and 700 MB.
Oh, that’s an understandable explanation.
I would like to briefly explain why I currently want to switch to AppImages: Both the installed version and the flatpak still have a bug with the AVFilter. Only AppImage works well.
For starting they don’t include a static version of fuse2 for launching the appimage itself
What is included is often a compromise
I have downloaded kdenlive-22.04.0-2-x86_64.AppImage, it start but there are dozens of warning about system’s libraries for undefined symbol: g_once_init_leave_pointer and undefined symbol: gst_audio_stream_align_new
Hello @Lolix,
I don’t quite understand your statements, but that’s not because of you, but because I’m not very familiar with Linux.
May I ask you: Is it normal that Manjaro cannot open all old AppImages from Kdenlive? If so, then my question is well answered.
btw I can open back to 20.04.0 and 18.08.3 (22.x, 21.x not tested), earlier version fails with:
This application failed to start because it could not find or load the Qt platform plugin "xcb"
in "".
Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, xcb.
Yes, because it still links to some system parts
Appimage guidelines says to build them on the oldest supported distro as the opposite could be problematic
IMO unfortunately appimage is somewhat bad at solving the problem it tries to solve, just see the error above
I could try to answer in more detail if you want
I just tested 22.04 for the sake of testing - indeed hangs on the splashscreen with a gazillion of errors if run from terminal, some of which clearly indicate poor appimage building, because it searched for libraries in home instead of usr or tmp, so someone used absolute paths while building the appimage…probably the biggest issue was gstreamer which this version did not like and suggested toggling some flag…and then theme errors, and dbus errors…it is just not worth debugging it. The newest version from the repos just works without any errors.
Plasma on Testing branch…
KDE Plasma Version: 6.2.2
KDE Frameworks Version: 6.7.0
Qt Version: 6.8.0
Kernel Version: 6.11.5-1-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 12 Ă— AMD Ryzen 5 5600G with Radeon Graphics
Graphics Processor: AMD Radeon Graphics
Product Name: B550M Steel Legend
The next version after the screenshot was fully themed.