AppImageLauncher icon indicating copy to clipboard operation
AppImageLauncher copied to clipboard

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

Open OZ1SEJ opened this issue 4 months ago • 1 comments

Pre-submit checks

  • [x] I checked for similar issues 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.

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.

OZ1SEJ avatar Aug 08 '25 08:08 OZ1SEJ

This is supposed to be fixed with the upcoming 3.0 (currently alpha).

See e.g.:

  • https://github.com/audacity/audacity/issues/8790#issuecomment-2889892542
  • https://forum.cursor.com/t/0-47-9-failed-to-launch-fuse-memory-allocation-failed/68394
  • ...

Although there has been little activity recently. I hope it will get an official release soon, so that distros can pick this up.

ensonic avatar Aug 11 '25 08:08 ensonic