Add a check for whether lib64z1 / zlib1g-dev pkg is installed.

[voxpop9]

Currently testing on a Radxa Zero 3W running the Radxa Debian OS. Ran the script and it didn't work the first time, found out there was a missing library which was installed via sudo apt install zlib1g-dev. Script ran fine and was able to install the app and it's related dependancies and auto start too.

[f-io]

Hey, thanks for pointing that out! Are you sure it was zlib1g-dev? That should only be required for building. For running the AppImage, the zlib1g runtime should be enough. Could you check if it was actually just missing zlib1g? I prefer to only install packages that are essential for running the app, I’m not a fan of adding extra packages unless they’re really needed.

[voxpop9]

I have and indeed the OS had zlib1g. I even updated the package and it was at most up to date and the app still would not run until I checked online for the error: error while loading shared libraries: libz.so: cannot open shared object file: No such file or directory, the suggested solution (or supoosedly a workaround as AppImage/AppImageKit#1092 and AppImage/AppImageKit#964 talk about this issue more indepth) fixed it for me. Maybe those 2 issues highlight the problem better.

[f-io]

This looks like an electron-builder linking issue. The -dev package only provides the unversioned libz.so symlink to libz.so.1. Could you verify whether creating the symlink manually works on your side (without installing zlib1g-dev)?

sudo ln -s /usr/lib/aarch64-linux-gnu/libz.so.1 /usr/lib/aarch64-linux-gnu/libz.so

[voxpop9]

Yup confirmed working. Removed zlib1g-dev and ran without your command to confirm the issue is back. App did not run. Ran your command and ran the app, works again. Suggestion might be to run that command in case

[f-io]

Thanks for confirming! I’d rather not add the symlink to the installer though, that just works around the symptom. Better to fix it upstream in electron-builder/AppImage so it links against libz.so.1 properly.

[voxpop9]

In that case, maybe put a disclaimer about this issue and a temporary workaround for it on the main page. Otherwise, the script works on debian based oses at least.

[f-io]

I’ll double-check, but I think this only affects arm64. On stock Raspberry Pi OS (also Debian-based) it probably doesn’t show up since build-essential is preinstalled. I’ve also never seen this on my Debian 13 (Trixie) system, which I use to test the x86 builds.