Last AppImage version
Where can I download the last Linux version of the PrusaSlicer that is still an AppImage?
Best Answer by Walter Layher:
Try one of the previous releases on github. They stopped providing AppImages because they could not offer one version that would cover all linux distributions and decided on providing one flatpak version for linux from now on. The reasons were mentioned in the release notes on github. But those flatpaks are also without problems and have their own quirks. You could still try to build PrusaSlicer from source on your system.
RE: Last AppImage version
Try one of the previous releases on github. They stopped providing AppImages because they could not offer one version that would cover all linux distributions and decided on providing one flatpak version for linux from now on. The reasons were mentioned in the release notes on github. But those flatpaks are also without problems and have their own quirks. You could still try to build PrusaSlicer from source on your system.
RE: Last AppImage version
Thanks, I see 2.8.1 is the last AppImage on Github, I’ll give that I try.
It needs to be installed on a secure computer that has no internet access, so I need to download the complete package and then transfer it to the secure computer to install it. This is not possible with flatpacks because then you only download an installer. So in the long run I’ll probably need to move to Cura anyway if I want/need new features or support for newer printers.
RE: Last AppImage version
The build instructions for PrusaSlicer found on github work on Ubuntu and Debian. On others probably too, but I only have tested these two. If you are on one of those systems, you may have to install some additional -dev packages there but it is feasible.
RE: Last AppImage version
It needs to be installed on a secure computer that has no internet access, so I need to download the complete package and then transfer it to the secure computer to install it.
Never used it myself, but have you tried flatpak create-usb?
RE: Last AppImage version
It needs to be installed on a secure computer that has no internet access, so I need to download the complete package and then transfer it to the secure computer to install it.
Never used it myself, but have you tried flatpak create-usb?
That looks quite interesting. For now I’ll just use the last AppImage, but this could very well be the way to move forward in case of a printer upgrade.
RE:
Stupidity that they removed the last AppImage file
anyone at all got the last version provided ?
RE: Last AppImage version
What are you talking about, they are still there and available. I can click on to download without a problem.
RE:
Why did you stop the builds of appimage? why? I dont have flatpak since i dont want its trash installed.
Here are my 10 reasons i dont have and never will have flatpak.
1. Storage Overhead Flatpak apps bundle their dependencies, leading to significant disk space usage. Multiple apps may include duplicate libraries, wasting storage compared to traditional package management.
2. Memory Consumption Each Flatpak app runs with its own runtime environment, consuming more RAM than native applications that share system libraries.
3. Slower Startup Times The sandboxing and runtime initialization can cause noticeably slower application launch times compared to native packages.
4. Limited System Integration Sandboxing restrictions can prevent apps from properly integrating with desktop environments, affecting features like file associations, system themes, and native dialogs.
5. Permission Complexity Managing Flatpak permissions can be confusing for users. Apps may request broad permissions that compromise the security benefits of sandboxing.
6. Reduced Performance The additional abstraction layers and sandboxing overhead can impact application performance, especially for resource-intensive software.
7. Dependency on Flathub Heavy reliance on centralized repositories like Flathub creates potential single points of failure and limits package availability.
8. Maintenance Burden System administrators must manage both traditional packages and Flatpak runtimes, increasing complexity and maintenance overhead.
9. Inconsistent User Experience Flatpak apps may not follow system-wide settings for themes, fonts, or accessibility options, creating an inconsistent desktop experience.
10. Security Trade-offs While sandboxing provides isolation, the broad permissions often required by complex applications can negate security benefits, while the large attack surface of bundled dependencies may introduce vulnerabilities.
So when are we going to have back the app image builds?
RE: Last AppImage version
Just follow the github build instructions for linux: https://github.com/prusa3d/PrusaSlicer/blob/master/doc/How%20to%20build%20-%20Linux%20et%20al.md
I am not a developer and I found that it is not that hard to get it to work. If you run into problems you can ask again here. But the instructions are pretty straightforward.
RE:
I am a system administrator and obviously i know how to build. but the point is that its not the offical app image, i dont have notifications of new updates and other things. That is why i would avoid building it.
Thanks for your help
RE: Last AppImage version
You get notifications of new versions and config updates this way as well (at least this works on my system). You just have to update the source via git and build again.
RE: Last AppImage version
I am on a mail list and got a message about an Appimage test. Then it was taken over and is being maintained. I am using it. At 2.9.2 now.