AppImage does not run with AppImageLauncher

[adazem009]

Issue type

Other type of issue

Bug description

Latest nightly builds don't work at all on Linux when AppImageLauncher is installed. The AppImage crashes with this error message:

execv error: No such file or directory

When I try to extract it using --appimage-extract:

This doesn't look like a squashfs image.
Failed to open squashfs image

Steps to reproduce

1. Download a nightly build of MuseScore or an artifact from GitHub actions.
2. Install AppImageLauncher.
3. Mark the AppImage as executable and execute it.

Screenshots/Screen recordings

No response

MuseScore Version

4.2.0

Regression

Yes, this used to work in a previous version of MuseScore 4.x

Operating system

Ubuntu 22.04 (KDE Plasma 5.24.7)

Additional context

I think this PR is related: #18785
My system has both version 2 and 3 of libfuse installed.

[AntonioBL]

Ciao.
I tried to test this inside a virtual machine with Ubuntu 22.04, KDE 5.92.0 Plasma 5.24.7, but I could not reproduce this behavior: the Appimage was running fine.
Are you launching the Appimage via a launcher, or directly launching it from the command line?

[adazem009]

Ciao.
I tried to test this inside a virtual machine with Ubuntu 22.04, KDE 5.92.0 Plasma 5.24.7, but I could not reproduce this behavior: the Appimage was running fine.
Are you launching the Appimage via a launcher, or directly launching it from the command line?

I have AppImageLauncher installed and I clicked "run once" to run the AppImage.

[AntonioBL]

Can you please try to launch the AppImage via command line and see if it gives problems?

Edit: I found that the problem is an interplay between AppImageLauncher and the new AppImage format. If I install AppImageLauncher, every time I try to run the AppImage, it tries to pass through the launcher, and somehow also even if use env variable APPIMAGELAUNCHER_DISABLE=true
Only if I uninstall AppImageLauncher then I can run this new format AppImage.

[shoogle]

Looks like we're waiting on TheAssassin/AppImageLauncher#585 to be resolved. In the meantime, it's a choice between:

1. Continue using the new (static) AppImage runtime, in which case AppImageLauncher users need to uninstall AppImageLauncher in order to use our nightly builds.

2. Revert back to using the old (non-static) AppImage runtime, in which case Ubuntu users need to install libfuse2 to run our nightly builds (which they have probably done already in order to run our stable builds).

On that basis I think we should probably revert back for now. @AntonioBL, would you be willing to do the honours?

[AntonioBL]

Ok, done: #18854
It is a pity that we cannot already use the new static runtime...

[shoogle]

@AntonioBL, Indeed! Thanks for testing and reverting it for us. Let's hope it gets supported soon in AppImageLauncher.

[adazem009]

@AntonioBL, Indeed! Thanks for testing and reverting it for us. Let's hope it gets supported soon in AppImageLauncher.

Should this issue be closed and #18633 reopened until it gets supported in AppImageLauncher?

[shoogle]

@adazem009, good point. The fixes are mutually exclusive, and we've chosen to prioritise this issue for now as explained here.