Gtk-WARNING GLIBC version not found (latest release)

[theofficialgman]

Description of the issue
Warnings of this type are printed in the log repeatedly

(prusa-slicer:3515): Gtk-WARNING **: 21:14:17.802: /tmp/.mount_PrusaSkkdLoL/shared/lib/libc.so.6: version `GLIBC_2.38' not found (required by /usr/lib/aarch64-linux-gnu/gtk-3.0/3.0.0/immodules/im-fcitx5.so)

(prusa-slicer:3515): Gtk-WARNING **: 21:23:54.272: Loading IM context type 'fcitx5' failed

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

• Hardware: Nintendo Switch
• OS: Ubuntu Noble 24.04

Steps to reproduce the reported issue (if applicable)
Run the appimage

Screenshots (if applicable)

[theofficialgman]

I will note that the program seems to run fine regardless of these errors (but it does segfault on closing but that could just unrelated).

So it seems that the glibc version in the appimage is lower than the glibc version of the system and something from within the appimage is trying to load im-fcitx5.so and it is not available in the appimage so it fallsback to the system version which then can't load with the old glibc from the appimage.

[theofficialgman]

CC @probonopd @Samueru-sama

[probonopd]

One way to solve is to bundle all needed libraries in the AppImage as described here:

• AppImage for 2.9.0 and later prusa3d/PrusaSlicer#13653

[Samueru-sama]

@probonopd This repo is already using sharun.

@theofficialgman The issue here is that the gtk immodules were not bundled, in fact none of the gtk3 dir was bundled oddly enough.

[davidk]

Ubuntu Noble 24.04 and Debian Trixie are ahead of Bookworm so the AppImage needs some more padding in places - i've bundled in a few more things to help with compatibility, both from probonopd's repo and some extras to patch up the console spam that happens on Ubuntu Noble

Uploaded here for testing: https://github.com/davidk/PrusaSlicer-ARM.AppImage/releases/download/version_2.9.2/PrusaSlicer-2.9.2-aarch64-trixie.AppImage

Also, I have not been able to track down the cause of the segfault - more eyes welcome - as mentioned, it doesn't seem to affect core functionality