Hello David.

Thanks for all your effort building AppImages for ARMs. We at Prusa Research are now considering to integrate your effort into our build system, the main driver being adoption of chromebooks by US schools and the Linux on Chromebook effort, which is quite usable including OpenGL HW virtualization.

I suppose you are building your ARM AppImage builds on a R-PI.

Do you build both 32bit and 64 bit builds on the same R-Pi device running the same 64bit image? What image are you running?

Did you consider cross-compiling on an X86-64 box?

How long does the compilation take on your R-PI box? Are your compiling on an external USB SSD or on an SD card? We are compiling our images on an external SSD and the compilation process takes around 45 minutes.

This has been added to the Pi-Apps Raspberry Pi app store.

You should expect a spike in the number of downloads, as Pi-Apps has over 50,000 users.

I have deployed the last 2.3.0-armhf.Appimage
And executing the mommand:
sudo apt-get install -y git cmake libboost-dev libboost-regex-dev libboost-filesystem-dev
libboost-thread-dev libboost-log-dev libboost-locale-dev libcurl4-openssl-dev libwxgtk3.0-dev
build-essential pkg-config libtbb-dev zlib1g-dev libcereal-dev libeigen3-dev libnlopt-cxx-dev
libudev-dev libopenvdb-dev libboost-iostreams-dev libnlopt-dev libdbus-1-dev imagemagick
libgtk-3-dev libwxgtk3.0-gtk3-dev

But i have this error on app startup:
prusa-slicer: error while loading shared libraries: libgmpxx.so.4: cannot open shared object file: No such file or directory

The application doesn't not start.

Hi David,
Prusa are having difficulties with the rpi release for 2.60 alpha 2, so they are probably going to leave it till the next release.
Quote:
"We are having technical issues rolling out the RPi build and decided not to hinder the alpha release. Depending on when we manage to fix them, we will either attach them to 2.6.0-alpha2 or include them with the follow-up releases."

You could be a hero!! If you've got the time, of course. :-)
Cheers,
Eric

• jq
• curl
• libcgal: extra dependencies need to be added or apt install -f

Build details: Using GTK3 AppImage build
Version: 2.3.0
Arch: arm64/aarch64
Run: Using X over SSH (ssh -X pi@ ... )

Bug: Application hard crashes when attempting to add a file (using the 'add' button within PrusaSlicer). Last message in terminal is: No GSettings schemas are installed on the system

Hello, I'm a novice so forgive me if this turns out to be a waste of your time. I couldn't get the 32 bit appimage version to run without a segmentation fault without first copying the contents of my non-appimage installation located at "/home/pi/Desktop/Prusa/resources/profiles" to the "/usr/local/share/PrusaSlicer/profiles". After all the files were copied over the 32bit appimage runs correctly.

I installed the ARM64 AppImage just now and ran into the mentioned problems. I also installed et "extra" .deb-package, to no avail.

I already had the AppImage for Alpha3 on my system, which I have been using with success since you released it. Thanks!

Description of the issue
Core dumps immediately on running the appimage.

Hardware environment and OS that is being used to run PrusaSlicer-ARM.AppImage

• Hardware: Raspberry Pi 5 8GB
• OS: PiOS Bookworm ARM64

Description of the issue

• PrusaSlicer doesn't start, fails with errors related to pixbuf.

Hardware environment and OS that is being used to run PrusaSlicer-ARM.AppImage

• Raspberry Pi 4 (8GB)
• OS = Debian GNU/Linux 11 (bullseye)
• Linux pi4 5.15.84-v8+ #1613 SMP PREEMPT Thu Jan 5 12:03:08 GMT 2023 aarch64 GNU/Linux
• Fresh install of Raspbian Lite. + xserver / xinit / i3 etc ...

Steps to reproduce the reported issue (if applicable)

• Install the dependencies as indicated in the doc.
• Download the appimage
• chmod +x then
  ./PrusaSlicer-version_2.6.0-alpha6-aarch64.AppImage

[2023-04-16 18:00:00.641626] [0x0000007fac61d040] [trace] Initializing StaticPrintConfigs

(prusa-slicer:16888): Gtk-WARNING **: 18:00:05.473: Could not find the icon 'dialog-question'. The 'hicolor' theme
was not found either, perhaps you need to install it.
You can get a copy from:
http://icon-theme.freedesktop.org/releases

(prusa-slicer:16888): Gtk-WARNING **: 18:00:11.282: Could not load a pixbuf from /org/gtk/libgtk/icons/16x16/status/image-missing.png.
This may indicate that pixbuf loaders or the mime database could not be found.
**
Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load /org/gtk/libgtk/icons/16x16/status/image-missing.png: Unrecognised image file format (gdk-pixbuf-error-quark, 3)
Bail out! Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load /org/gtk/libgtk/icons/16x16/status/image-missing.png: Unrecognised image file format (gdk-pixbuf-error-quark, 3)
Aborted

hicolor-icon-theme is installed on the system.
Tested with 2.5.1 and 2.5.2 minimal AppImage, same results, same error messages.

running the ./build.sh to make a appimage for ubuntu bionic aarch64
The build script seems to not be working at all

I have all the dependencies installed but the .yml is just printed to the terminal
output.txt

Hello David,

I really appreciate your work. I am trying to download PrusaSlicer for a Raspberry Pi 4 Model B with Raspbian. I've downloaded the full repository and ran ./build.sh in the terminal. Everything runs fine until it prompts me to choose between the full version, the minimum version, or both. When I execute any command at that point, it gives me the following message:

FileNotFoundError: [Errno 2] No such file or directory: 'AppImageBuilder-armhf-full-version_2.7.2.yml'

I tried changing the names of the yml files but I see that there is no improvement

Hi David,
This is an excellent piece of work, and it runs very well indeed on my 4Gb, 128Gb SSD setup.
I probably don't spend enough time in Linux Land, because I had no idea what an AppImage was. A bit of Google research sorted that out.
When I first ran it I got an:
prusa-slicer: error while loading shared libraries: libnlopt.so.0: cannot open shared object file: No such file or directory
No worries, an installation of libnlopt-dev sorted it out.

When double clicked the options of executing it, or executing it from a terminal is interesting.
Both work, but the terminal option gives a number of errors, such as:

__(prusa-slicer:7496): Gtk-CRITICAL **: 17:50:28.437: IA__gtk_tree_view_scroll_to_cell: assertion 'tree_view->priv->tree != NULL' failed

(prusa-slicer:7496): Gtk-CRITICAL **: 17:50:28.437: IA__gtk_tree_view_scroll_to_cell: assertion 'tree_view->priv->tree != NULL' failed
[2020-01-24 17:50:28.448357] [0xb1e18010] [error] Unable to enumerate HID devices
[2020-01-24 17:50:37.030211] [0xb1e18010] [error] Unable to enumerate HID devices__

Great work, many thanks, I had the pi4 with nothing for it to do, but now ...
Cheers,
Eric

Thanks for providing this AppImage.

 $ uname -a
Linux raspberrypi 5.4.51-v8+ #1327 SMP PREEMPT Thu Jul 23 11:11:34 BST 2020 aarch64 GNU/Linux
 $ ./PrusaSlicer-2.3.0-alpha2-armhf.AppImage 
./PrusaSlicer-2.3.0-alpha2-armhf.AppImage: error while loading shared libraries: libz.so: cannot open shared object file: No such file or directory

Could you add a build for 64-bit raspberry os?

Description of the issue
When trying to install the dependencies to run the aarch64 image on a fresh installation of Raspberry Pi OS i get this errors

E: Unable to locate package libwxgtk3.0-gtk3-dev
E: Couldn't find any package by glob 'libwxgtk3.0-gtk3-dev'
E: Couldn't find any package by regex 'libwxgtk3.0-gtk3-dev'

Hardware environment and OS that is being used to run PrusaSlicer-ARM.AppImage
PrusaSlicer-version_2.6.1-aarch64.AppImage

• Hardware [e.g. Raspberry Pi 4 (4GB), Raspberry Pi 4 (8GB)]:
• RaspBerry Pi 400
• OS [e.g. Raspberry Pi OS (32-bit/armhf), Ubuntu Mate 21.04 (64-bit/aarch64)]:
• Raspberry Pi OS 64-bit

Steps to reproduce the reported issue (if applicable)
running

sudo apt-get install -y git cmake libboost-dev libboost-regex-dev libboost-filesystem-dev libboost-thread-dev libboost-log-dev libboost-locale-dev libcurl4-openssl-dev build-essential pkg-config libtbb-dev zlib1g-dev libcereal-dev libeigen3-dev libnlopt-cxx-dev libudev-dev libopenvdb-dev libboost-iostreams-dev libgmpxx4ldbl libnlopt-dev libdbus-1-dev imagemagick libgtk2.0-dev libgtk-3-dev libwxgtk3.0-gtk3-dev fuse libfuse2

get the mentioned error

Update: I got it running without that dependency

Description of the issue
There is no installation candidate for "libwxgtk3.0-dev" on latest 64bit Raspberry PiOS, readme apt-get fails.

Hardware environment and OS that is being used to run PrusaSlicer-ARM.AppImage

• Raspberry Pi >=3 (I use Pi400):
• latest 64bit Raspberry PiOS (Bullseye)

Steps to reproduce the reported issue (if applicable)
"sudo apt-get install ..." fails:

Screenshots (if applicable)

Reading state information... Done
Package libwxgtk3.0-dev is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'libwxgtk3.0-dev' has no installation candidate
pi@pi400-64:~ $ 

Fix is simply removing last package from the apt-get command, "PrusaSlicer-version_2.4.1-aarch64.AppImage" runs fine on 64bit PiOS then.

Describe the feature and if there are any other alternatives (if applicable)
It would be nice to have also a no GUI build if you want to use the slicing feature only

Does this feature resolve a problem?
You would be able to slice files also if your embedded system has no display at all

Additional context (screenshots, diagrams, links to external documentation etc)
prusa3d/PrusaSlicer#7521 should explain how it can be done. I tried to compile it on my Raspberry Pi 3 with 32-bit Bullseye installed, but the compilation process always got stuck.

Hi David,
I have Ubuntu Mate 20.10 groovy with aarch64 / arm 64 architecture on Raspberry Pi 400
Passing 'uname -a' outputs >
Linux RPi400-UbuMateArch64-2010 5.8.0-1013-raspi #16-Ubuntu SMP PREEMPT Thu Jan 14 06:28:38 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux
While 'Screenfetch' command outputs >
OS: Ubuntu 20.10 groovy Kernel: aarch64 Linux 5.8.0-1013-raspi Shell: zsh 5.8 DE: MATE 1.24.1
etc..
Have tried both the 'PrusaSlicer-2.3.0-GTK2-aarch64.AppImage' and the 'PrusaSlicer-2.3.0-GTK23-aarch64.AppImage'. They have extra permissions set but return the following error >
prusa-slicer: error while loading shared libraries: libboost_log.so.1.67.0: cannot open shared object file: No such file or directory
When i try to install the required dependencies OR try to build using the build.sh script i get the following error >
Package libwxgtk3.0-dev is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source
I see from this Stack Exchange Q&A that > libwxgtk3.0-dev was changed to libgtk3.0-gtk3-dev in 20.04.
I have libgtk3.0-gtk3-dev already installed.
My source list at /etc/apt/sources.list.d contains the following deb http://ppa.launchpad.net/ubuntu-mozilla-security/ppa/ubuntu/ groovy main.
Any idea how to work around this?
Cheers, Michael.

the title describes the request. please don't mark alphas as release versions.

I get Segmentation faults when I try and run the AppImage on either of my Pi4s. One is a 1GB and one is a 2GB, running octopi and buster lite respectively, neither with a GUI. Do they need to be 4GB models to install, I didn't see that as a requirement anywhere on your page?

pi@bupherspi:~/download $ ./PrusaSlicer-2.2.0-armhf.AppImage
Segmentation fault
pi@bupherspi:~/download $

David, thanks very much for your work, I've been able to follow the development of the 2.3.x slicer on my pi4 without any risks to my PC based slicing activities. Really appreciate it.

This new, final, AppImage version seems to have an additional dependency. I can't remember the exact error message, but it was along the lines of there's a missing shared library - libwx_gtk3u_core-3.0.so.0.

I did re-do the apt-get install that you quote and reboot but that wasn't the problem. My Google research pointed me to the libwxgtk3.0-gtk3-0v5 library for the missing libwx_gtk3u_core-3.0.so.0 which I installed and now 2.3.0 works.

The program start-up is a little different from previous versions; there's a bit of wallpaper flashing and the Prusa Slicer Flash screen doesn't show, or maybe very, very briefly. I haven't yet tried a PC version of 2.3.0 so I don't know if this behaviour is reflected in that version too. Makes me wonder if I got the right library for libwx_gtk3u_core-3.0.so.0.

Anyway, thanks again,
Eric

Hello

1st of all, thank you for this effort ! this is a great thing.

but i do have a problem.

Followed all steps and getting this error,

common.copy /home/guy/Downloads/PrusaSlicer-ARM.AppImage/PrusaSlicer/deps/build/destdir/usr/local/lib/cmake/boost_regex-1.75.0/boost_regex-config.cmake
common.copy /home/guy/Downloads/PrusaSlicer-ARM.AppImage/PrusaSlicer/deps/build/destdir/usr/local/lib/cmake/boost_regex-1.75.0/boost_regex-config-version.cmake
...updated 15986 targets...
[ 85%] Completed 'dep_Boost'
[ 85%] Built target dep_Boost
make: *** [Makefile:103: all] Error 2
Traceback (most recent call last):
File "/usr/local/bin/appimage-builder", line 8, in
sys.exit(main())
File "/usr/local/lib/python3.9/dist-packages/appimagebuilder/main.py", line 50, in main
invoker.execute(commands)
File "/usr/local/lib/python3.9/dist-packages/appimagebuilder/invoker.py", line 29, in execute
command()
File "/usr/local/lib/python3.9/dist-packages/appimagebuilder/commands/run_script.py", line 82, in call
raise RuntimeError("Script exited with code: %s" % _proc.returncode)
RuntimeError: Script exited with code: 2

Please help.

The system is Pi 4 B 8 GB
os is:
guy@fjord:~/Downloads/PrusaSlicer-ARM.AppImage $ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

Thank you
Guy

Hi guys, this package is little bit older than newest RPI OS (64bit RPI OS on RPI400). You AppImage use/needs FUSE2, but latest RPI is based on FUSE3. Please add this as a workaround for PrusaSlicer v2.5.0 on latest 64bit RPI OS:
sudo apt-get install fuse libfuse2

BTW my OS:

cat /etc/os-release 
PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

Description of the issue
Attempting to use the appimage on anything other than debian buster will not work as the linker attempts to find libboost 1.67 EXACTLY. No newer or older version will work

prusa-slicer: error while loading shared libraries: libboost_log.so.1.67.0: cannot open shared object file: No such file or directory

I have the same issue with building myself... the version of boost is hardcoded into the linker

	libboost_log.so.1.67.0 => /usr/lib/aarch64-linux-gnu/libboost_log.so.1.67.0 (0x0000007fa747e000)

	libboost_filesystem.so.1.67.0 => /usr/lib/aarch64-linux-gnu/libboost_filesystem.so.1.67.0 (0x0000007fa7454000)

	libboost_thread.so.1.67.0 => /usr/lib/aarch64-linux-gnu/libboost_thread.so.1.67.0 (0x0000007fa741a000)

	libboost_locale.so.1.67.0 => /usr/lib/aarch64-linux-gnu/libboost_locale.so.1.67.0 (0x0000007fa7315000)

	libboost_chrono.so.1.67.0 => /usr/lib/aarch64-linux-gnu/libboost_chrono.so.1.67.0 (0x0000007fa72fc000)

	libboost_system.so.1.67.0 => /usr/lib/aarch64-linux-gnu/libboost_system.so.1.67.0 (0x0000007fa6f21000)

	libboost_iostreams.so.1.67.0 => /usr/lib/aarch64-linux-gnu/libboost_iostreams.so.1.67.0 (0x0000007fa6ef5000)

	libboost_regex.so.1.67.0 => /usr/lib/aarch64-linux-gnu/libboost_regex.so.1.67.0 (0x0000007fa6dd9000)

	libboost_atomic.so.1.67.0 => /usr/lib/aarch64-linux-gnu/libboost_atomic.so.1.67.0 (0x0000007fa544c000)

	libboost_date_time.so.1.67.0 => /usr/lib/aarch64-linux-gnu/libboost_date_time.so.1.67.0 (0x0000007fa542a000)

	libboost_iostreams.so.1.65.1 => /usr/lib/aarch64-linux-gnu/libboost_iostreams.so.1.65.1 (0x0000007fa347a000)

Hardware environment and OS that is being used to run PrusaSlicer-ARM.AppImage

• Hardware: literally any arm64 system
• OS : anything other than buster

Description of the issue
I can't run this appimage, it shows these info.
I actually don't know too much about how to use rasperry pi, I just an 3d fan.

I got these info:

./PrusaSlicer-version_2.4.2-aarch64.AppImage
[2022-04-28 11:44:10.056142] [0x0000007fa1682040] [trace] Initializing StaticPrintConfigs
Segmentation fault

Hardware environment and OS that is being used to run PrusaSlicer-ARM.AppImage

• Hardware Raspberry Pi 4 (4GB)
• OS [Raspberry Pi OS (64-bit/aarch64)]:
• PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
  NAME="Debian GNU/Linux"
  VERSION_ID="11"
  VERSION="11 (bullseye)"
  VERSION_CODENAME=bullseye
  ID=debian

Hi David,
First, I'm so happy with your work to bring an easy way to use The Prusa Slicer on, for me, a separate system, where I can really play with the new stuff in complete isolation from my usual Windows box. Thanks very much. It works very well.

This latest Alpha 2 release has no AppImage in it's assets, do I need to build it, or am I too quick off the mark and the AppImage itself is on it's way, or maybe I'm looking in the wrong place.

Thanks again,
Cheers,
Eric

After installing the dependencies and running the app image, I’m getting the following error:

“../arc/unix/glx11.cpp(589): assert “ok” failed in GetGLXVersion(): GLX version not found.”

Any idea on what I might’ve done wrong? I’ve also go into raspi-config > Advanced and enabled the GL drivers.

I tried your AppImage builds for fedora 34 aarch64, both gtk3 and gtk2 fail to start.

prusa-slicer: error while loading shared libraries: libboost_log.so.1.67.0: cannot open shared object file: No such file or directory

Package boost-log-1.75.0-4.fc34.aarch64 is currently in the repository.

So I believe I followed the directions correctly (I am still relatively new with linux/raspberry pi's) but when attempting to open (using ./PrusaSlicer-2.3.0-GTK2-armhf.AppImage) I get this error

`pi@raspberrypi:~/Downloads $ ./PrusaSlicer-2.3.0-GTK2-armhf.AppImage
fuse: device not found, try 'modprobe fuse' first

Cannot mount AppImage, please check your FUSE setup.
You might still be able to extract the contents of this AppImage
if you run it with the --appimage-extract option.
See https://github.com/AppImage/AppImageKit/wiki/FUSE
for more information
open dir error: No such file or directory
pi@raspberrypi:~/Downloads $
`