Prusa slicer not working
Confirmations
- [x] I searched for similar bug reports in https://github.com/Botspot/pi-apps/issues and found none were relevant.
- [x] I tried updating Pi-Apps and the issue is still not fixed. How to update Pi-Apps?
- [x] IMPORTANT: I promise to respond to comments on this issue and write a good bug report https://www.softwaretestinghelp.com/how-to-write-good-bug-report/
What happened?
Prusa Slicer doesn't launch
Description
I installed Prusa Slicer 2.9.1 from Pi app (via install button) and doesn't work. I tried the terminal comand you indicate but this error appears,
What are your system specs (run the following command in your terminal)?
OS: Debian GNU/Linux 12 (bookworm)
OS architecture: 64-bit
Last updated Pi-Apps on: 05/13/2025
Latest Pi-Apps version: 05/13/2025
Kernel: aarch64 6.12.25+rpt-rpi-v8
Device model: Raspberry Pi 400 Rev 1.0
SOC identifier: bcm2711
Machine-id (hashed): 3e9f12ae418a29baace58b94c77a6839a269087a
Serial-number (hashed): e7fbc4792e6a7fd91d2b361f720e47f8ae978bb8
Cpu name: Cortex-A72
Ram size: 3.79 GB
Raspberry Pi OS image version: 2025-05-13
Language: en_US.UTF-8
(Recommended) Error log? Terminal output? Debug messages?
MESA_GL_VERSION_OVERRIDE=3.3 /opt/PrusaSlicer.AppImage
/tmp/.mount_PrusaSIeq6Nn/usr/bin/prusa-slicer: error while loading shared libraries: libwebkit2gtk-4.0.so.37: cannot open shared object file: No such file or directory
Hello there 👋 Thanks for submitting your first issue to the Pi-Apps project! We'll try to get back to you as soon as possible. In the meantime, we encourage you join our Discord server, where you can ask any questions you might have.
Please respond as soon as possible if a Pi-Apps maintainer requests more information from you. Stale issues will be closed after a lengthy period of time with no response.
Confirmations
- [x] I searched for similar bug reports in https://github.com/Botspot/pi-apps/issues and found none were relevant.[x] I tried updating Pi-Apps and the issue is still not fixed. How to update Pi-Apps?[x] IMPORTANT: I promise to respond to comments on this issue and write a good bug report https://www.softwaretestinghelp.com/how-to-write-good-bug-report/
What happened?
Prusa Slicer doesn't launch
Description
I installed Prusa Slicer 2.9.1 from Pi app (via install button) and doesn't work. I tried the terminal comand you indicate but this error appears,
What are your system specs (run the following command in your terminal)?
OS: Debian GNU/Linux 12 (bookworm) OS architecture: 64-bit Last updated Pi-Apps on: 05/13/2025 Latest Pi-Apps version: 05/13/2025 Kernel: aarch64 6.12.25+rpt-rpi-v8 Device model: Raspberry Pi 400 Rev 1.0 SOC identifier: bcm2711 Machine-id (hashed): 3e9f12ae418a29baace58b94c77a6839a269087a Serial-number (hashed): e7fbc4792e6a7fd91d2b361f720e47f8ae978bb8 Cpu name: Cortex-A72 Ram size: 3.79 GB Raspberry Pi OS image version: 2025-05-13 Language: en_US.UTF-8
(Recommended) Error log? Terminal output? Debug messages?
MESA_GL_VERSION_OVERRIDE=3.3 /opt/PrusaSlicer.AppImage /tmp/.mount_PrusaSIeq6Nn/usr/bin/prusa-slicer: error while loading shared libraries: libwebkit2gtk-4.0.so.37: cannot open shared object file: No such file or directory
webkit2gtk appears to not be installed, install it using sudo apt install libwebkit2gtk-4.0-37 and it should be solved.
Its a pretty odd requirement for an appimage to require a specifically versioned system library like this. The whole point of appimages is you include enough libraries in them to NOT be so dependent in system libraries that change between OS releases.
In any case, it looks like this was done by design @Botspot and we should be changing to a new release name which includes these libraries. See here for details https://github.com/davidk/PrusaSlicer-ARM.AppImage/releases/tag/version_2.9.1 . The old release name isn't even available anymore in the latest version, which is why the auto updater hasn't been pulling it in. If all our supported systems work with the new release https://github.com/davidk/PrusaSlicer-ARM.AppImage/releases/download/version_2.9.2/PrusaSlicer-2.9.2-aarch64-full.AppImage we should switch over to it.
This should be fixed now with the newer appimages that include more system libraries.