Appimage load error

MLXQt · August 22, 2025, 12:50pm

Hi,
i have a problem with the last version of the AppImage v25.8.16.
I use Manjaro LXQt last stable update 6.12.41-1 and the last Shotcut version that works for me is the 25.05.11.
If i double click the AppImage it doesn’t load Shotcut and if i try from terminal i get this error:

Can’t open squashfs image: Bad address

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 FUSE · AppImage/AppImageKit Wiki · GitHub
for more information
execv error: No such file or directory

If i try ./Shotcut.AppImage i get this:

fuse: memory allocation failed
squashfuse 0.5.2 (c) 2012 Dave Vasilevsky

Usage: squashfuse [options] ARCHIVE MOUNTPOINT

I tried to extract manually and run it but it gave error.
So i tried this:

bsdtar -xf ./Shotcut.AppImage -C /home/HOMENAME/Shotcut/squash-root
bsdtar: Error opening archive: Unrecognized archive format

So i tried file and i got this:

file Shotcut.AppImage
Shotcut.AppImage: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), static-pie linked, BuildID[sha1]=b15b018a4f56042ad61c2b9e0504773f7da1ac38, stripped

My fuse packages are this:

Anybody has any idea?
Thanks.

P.S.: if you need some info please post the terminal command too.

shotcut · August 22, 2025, 4:47pm

The AppImage works for me on Pop!_OS 22.04. It looks like a problem on your system or some new problem in Manjaro since it cannot even be mounted.

MLXQt · August 24, 2025, 7:46am

Ok it works in Pop! but i’m using another distro. Shotcut v25.05.11 loads in my system but last version 25.8.16 not. Isn’t it possible that You made some changes in the new version that makes me get those errors?
I guess so because if the previous version loads, i don’t understand why the new doesn’t.
Isn’t possible to check if there is an error in the new appimage?

I tried file command and i got this:

LAST VERSION:

file Shotcut.AppImage
Shotcut.AppImage: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), static-pie linked, BuildID[sha1]=b15b018a4f56042ad61c2b9e0504773f7da1ac38, stripped

while for the previous version, that works, i get this:
PREVIOUS VERSION

~/Shotcut >>> file ShotcutWORKING.AppImage
ShotcutWORKING.AppImage: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=30e06184968532b6a9aa36f44ada39e4af0bda56, for GNU/Linux 2.6.32, stripped

there is a little difference and i don’t know if that’s the problem.
Moreover the last version is only 180MB, while the 25.5.11 is 250MB.
Is that ok?

I also tried v 25.07.26 and this one doesn’t load.
So something changes from 25.05.11 to 25.07.26.
Maybe something related to fuse or squashfuse or other?

MLXQt · August 24, 2025, 3:48pm

Ok solution is here:

Thanks anyway.

shotcut · August 24, 2025, 4:00pm

Something did change because the AppImage builder runs a script from AppImage GitHub repos to do the packaging.
It uses GitHub - AppImageCommunity/pkg2appimage: Tool and recipes to convert existing deb packages to AppImage in a container on a GitHub runner set to “ubuntu-latest”

pkg2appimage made this recent change from AppImageKit to appimagetool

But I do not know how that change could cause the problem you are facing. If anything, it looks like the more recent version with static-pie linked should be more system independent and compatible. I do not know the internals of AppImage. I am reading that there is an optional SquashFS kernel module that can mount this, and if that fails a squashfsfuse embedded into the AppImage executable is used. And if the latter does not work it tries to use squashfsfuse on your system.

shotcut · August 24, 2025, 4:09pm

I found these bugs in AppImageLancher project that match your failure. I also reproduced the problem in an Arch-based Garuda 2025 VM that I have; I think it installed AppImageLauncher by default. There are other but reports it links to.

github.com/TheAssassin/AppImageLauncher

Doesn't work, also now I can't run some appimages

opened 08:02AM - 08 Aug 25 UTC

OZ1SEJ

bug needs verification

### Pre-submit checks - [x] I [checked for similar issues](https://github.com/T…heAssassin/AppImageLauncher/issues?q=) beforehand, but could not find any, not even closed ones. I could not add my bug report to any existing issue. - [x] I am going to take the time to to fill in all the required details. I know that the bug report will be dismissed otherwise. ### Describe the bug I've installed the program using ``` $ sudo dpkg -i ./appimagelauncher_2.2.0-travis995.0f91801.bionic_amd64.deb ``` I've used it on prior Ubuntu installations where - as far as I remember - all I needed to do was execute an appimage, after which it would be integrated into the desktop environment. Now, running some appimages, e.g. `MuseScore-Studio-4.5.2.251141401-x86_64.AppImage` still works fine, but are not integrated into the desktop environment, and AppImageLauncher doesn't start. However, *some* appimage files that worked yesterday, for example `kdenlive-25.04.3-x86_64.AppImage` no longer work after installing AppImageLauncher; when starting this kdenlive appimage, I get ``` $ ./kdenlive-25.04.3-x86_64.AppImage QSocketNotifier: Can only be used with threads started with QThread fuse: memory allocation failed ``` Running `arduino-ide_2.3.6_Linux_64bit.AppImage` gives another error: ``` $ ./arduino-ide_2.3.6_Linux_64bit.AppImage QSocketNotifier: Can only be used with threads started with QThread [153406:0808/095817.747662:FATAL:setuid_sandbox_host.cc(158)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /tmp/.mount_arduinatKhqg/chrome-sandbox is owned by root and has mode 4755. ``` -although this may have had problems before. ### Expected behavior I expected the AppImageLauncher program to start when running appimages, and I definitely did *not* expect *some* `*.AppImage` files to no longer be able to run. ### Steps to reproduce the issue 1. Install Ubuntu 24.04.3 LTS 2. Download a few `*.AppImage` files 3. Download the file `appimagelauncher_2.2.0-travis995.0f91801.bionic_amd64.deb` 4. Install it using `sudo dpkg -i ./appimagelauncher_2.2.0-travis995.0f91801.bionic_amd64.deb` 5. Start various `*.AppImage` files from terminal ### Screenshots I don't see screenshots are relevant. ### Distribution and desktop environment This is a Lenovo ThinkPad T15 Gen 2i, 11th Gen Intel® Core™ i7-1165G7 × 8 running 64-bit Ubuntu 24.04.3 LTS with Wayland. ### Installed AppImageLauncher version The file `appimagelauncher_2.2.0-travis995.0f91801.bionic_amd64.deb` downloaded from [the latest release page](https://github.com/TheAssassin/AppImageLauncher/releases/latest). ### List of AppImages you tried - kdenlive-25.04.3-x86_64.AppImage (AppImageLauncher doesn't start, the AppImage isn't even able to run) - arduino-ide_2.3.6_Linux_64bit.AppImage (AppImageLauncher doesn't start, the AppImage isn't even able to run) - MuseScore-Studio-4.5.2.251141401-x86_64.AppImage (runs, but AppImageLauncher doesn't start) - UltiMaker-Cura-5.10.0-linux-X64.AppImage (runs, but AppImageLauncher doesn't start) ### Additional context Nothing relevant that I can think of.

github.com/audacity/audacity

AppImage is not starting on Ubuntu 22.04

opened 07:14AM - 19 May 25 UTC

kryksyh

Could not reproduce AU3-bug Linux

### Bug description AppImage fails to start or extract on Ubuntu 22.04.5. Repo…rted by @irrationalpie7 in https://github.com/audacity/audacity/issues/8787#issuecomment-2889167284 I'm running Ubuntu 22.04.5 LTS, so I picked this file from the ones you linked [audacity-linux-3.7.3-x64-22.04.AppImage](https://github.com/audacity/audacity/releases/download/Audacity-3.7.3/audacity-linux-3.7.3-x64-22.04.AppImage), but when I try to execute it (./audacity-linux-3.7.3-x64-22.04.AppImage) I get some sort of error about fuse. ``` (AppImageLauncher:3431846): GLib-CRITICAL **: 12:11:48.317: g_file_test: assertion 'filename != NULL' failed fuse: memory allocation failed squashfuse 0.5.2 (c) 2012 Dave Vasilevsky Usage: squashfuse [options] ARCHIVE MOUNTPOINT (null) options: -o offset=N offset N bytes into ARCHIVE to mount -o subdir=PATH mount subdirectory PATH of ARCHIVE -o notify_pipe=PATH named pipe that will receive 's' (success) or 'f' (failure) when the mountpoint is ready -o timeout=N idle N seconds for automatic unmount -o uid=N set file owner to uid N -o gid=N set file group to gid N FUSE options: -h --help print help -V --version print version -d -o debug enable debug output (implies -f) -f foreground operation -s disable multi-threaded operation -o clone_fd use separate fuse device fd for each thread (may improve performance) -o max_idle_threads the maximum number of idle worker threads allowed (default: -1) -o max_threads the maximum number of worker threads allowed (default: 10) fuse: memory allocation failed squashfuse 0.5.2 (c) 2012 Dave Vasilevsky Usage: squashfuse [options] ARCHIVE MOUNTPOINT (null) options: -o offset=N offset N bytes into ARCHIVE to mount -o subdir=PATH mount subdirectory PATH of ARCHIVE -o notify_pipe=PATH named pipe that will receive 's' (success) or 'f' (failure) when the mountpoint is ready -o timeout=N idle N seconds for automatic unmount -o uid=N set file owner to uid N -o gid=N set file group to gid N FUSE options: -h --help print help -V --version print version -d -o debug enable debug output (implies -f) -f foreground operation -s disable multi-threaded operation -o clone_fd use separate fuse device fd for each thread (may improve performance) -o max_idle_threads the maximum number of idle worker threads allowed (default: -1) -o max_threads the maximum number of worker threads allowed (default: 10) squashfuse 0.5.2 (c) 2012 Dave Vasilevsky Usage: squashfuse [options] ARCHIVE MOUNTPOINT (null) options: -o offset=N offset N bytes into ARCHIVE to mount -o subdir=PATH mount subdirectory PATH of ARCHIVE -o notify_pipe=PATH named pipe that will receive 's' (success) or 'f' (failure) when the mountpoint is ready -o timeout=N idle N seconds for automatic unmount -o uid=N set file owner to uid N -o gid=N set file group to gid N FUSE options: -h --help print help -V --version print version -d -o debug enable debug output (implies -f) -f foreground operation -s disable multi-threaded operation -o clone_fd use separate fuse device fd for each thread (may improve performance) -o max_idle_threads the maximum number of idle worker threads allowed (default: -1) -o max_threads the maximum number of worker threads allowed (default: 10) Can't open squashfs image: Bad address 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 execv error: No such file or directory ``` I tried going to https://github.com/AppImage/AppImageKit/wiki/FUSE as the error message directed, but when I tried running ./audacity-linux-3.7.3-x64-22.04.AppImage --appimage-extract to see if I was on the right track, I got the following output: This doesn't look like a squashfs image. Failed to open squashfs image ### Steps to reproduce 1. Download Audacity 3.7.3 appimage file 2. Execute it ### Expected behavior The app should start ### Actual behavior The app does not start ### Audacity Version Audacity 3.7.3 ### Operating system Linux ### Additional context _No response_

I thought the point of AppImage is that you do not need to install something to run it.

I uninstalled it using sudo pacman -R appimagelauncher, but I had to reboot in order to get the AppImage to work.

MLXQt · August 25, 2025, 5:18am

Ok, thanks.

awake · August 25, 2025, 4:30pm

This is the type of thing that has made me experiment with
Flatpak as an alternative to AppImage. Thus far, the Shotcut flatpak has worked perfectly for me, including updating automatically to the latest version. That said, this is still a new enough experiment that I don’t know if there are any “gotchas” waiting down the road …

shotcut · August 25, 2025, 5:48pm

AppImage has been quite a reliable thing until now. I do believe this issue may tarnish its reputation. It is due to a confluence of events: people making a tool to better integrate AppImage into the desktop, people install that or even some distros install it by default (Garuda), and an AppImage build tool change. Sadly, the launcher project has not yet released the fix (?) yet. Who knows how long it will take to release, get into distros, and then onto peoples’ systems! I will try to pin the AppImage build tool we use to the previous version.

shotcut · August 25, 2025, 7:18pm

I have a fix that is ready now. It is a newer version 25.8.25 instead of a repackage of the latest release version. I might choose to do that, but it is not convenient whereas daily build CI/CD is automated:

http://builds.us.meltytech.s3.amazonaws.com/shotcut/shotcut-linux-x86_64-25.8.25.AppImage

MLXQt · September 6, 2025, 8:02am

Thanks but it’s ok, i already solved it. I answered with the link to the solution. It was a problem with some residual files left by appimagelauncher when i unistalled it. Thanks anyway.

system · November 20, 2025, 12:51pm

This topic was automatically closed after 89 days. New replies are no longer allowed.