I downloaded CrealityPrint-V6.1.2.2458-x86_64-Release.AppImage and when I try to launch it, I get the following error:
/tmp/.mount_CrealiVfWYPS/bin/CrealityPrint: error while loading shared libraries: libwebkit2gtk-4.0.so.37: cannot open shared object file: No such file or directory
Great. I did some searching and stumbled upon, judging from the filename, a specific Ubuntu 24.02 version of the Creality Print Appimage called “CrealityPrint_Ubuntu2404-V6.1.2.2458-x86_64-Release.AppImage.” You know, it would have been nice to have been pointed to this version from the main website instead of requiring me to just happen upon it on Creality’s Github page, but anyway, I decided to give it a try and I get this error:
/tmp/.mount_CrealiWk9qru/bin/CrealityPrint: error while loading shared libraries: libusrsctp
.so.2: cannot open shared object file: No such file or directory
Yes, I ensured both versions are set to be executable. Does any QA go into the Linux releases or does whoever makes this just compile and upload it?
Ran into same problem with both. Decided to use Ubuntu24.04 App image. Just used apt to install missing library.
Use “apt search libusrsctp”. It’ll show you the package and if it’s installed. In my case it was “sudo apt install libusrsctp2” that fixed it.
Thanks, BeachGeek, but this isn’t working either. See, I thought the whole point of the Appimage was so that the program has all its dependencies and libraries packed in together so you didn’t have to install anything. I’ve upgraded to 6.2.0, still the same problems.
CrealityPrint-V6.2.0.2827-x86_64-Release.AppImage:
./CrealityPrint-V6.2.0.2827-x86_64-Release.AppImage
/tmp/.mount_CrealiAzmOHz/bin/CrealityPrint: error while loading shared libraries: libwebkit2gtk-4.0.so.37: cannot open shared object file: No such file or directory
CrealityPrint_Ubuntu2404-V6.2.0.2827-x86_64-Release.AppImage
./CrealityPrint_Ubuntu2404-V6.2.0.2827-x86_64-Release.AppImage
/tmp/.mount_CrealiFoGvdU/bin/CrealityPrint: error while loading shared libraries: libOSMesa.so.8: cannot open shared object file: No such file or directory
Those missing shared object files are installed and on the latest versions, but I thought the whole point of the Appimage was to have everything the app needs packaged in one file to allow it to pretty much run on any version of Linux.
I thought they were supposed to be self-contained, but a coworker told me anything not in the image will be pulled from the system.
Maybe there’s a option that toggles whether it does or not. I’ll dig into it after the weekend.
Edit:
“AppImages can use both bundled and system libraries. Generally, they prefer bundled libraries but will use system libraries if a bundled one is missing or unavailable. This approach allows for smaller AppImage sizes and better portability while still leveraging the system’s libraries where appropriate.”