Appimage lastest Version different to September 23

have the dependencies in the app image changed since september?

Manjaro Linux (yes I know not officially supported but it was running for years).
Tracker3 removed from gtk3 last version
Webkit2gtk installed
Fuse2 and 3 installed

I still have an old version installed 23.9.21.1010, this runs fine, the database stand 08.09.2023 opens, everything Ok.

After a long period of illness (knee surgery) today I downloaded the latest appimage Version 23.10.16.1070 ,this does not open, no error message.

Now I wonder what has changed? I still have a lot of catching up to do.
Is there any way for me to find out for myself what is different in the appimage?

In the latest version, Fuse2 is no longer required. This makes AppImage work out of the box on fresh Ubuntu install for example.

As for the error message, there must be an error somewhere.

Can you launch AppImage directly from terminal?

./Manager-linux-x64.AppImage

Hello lubos, thank you for replay
the only error i can see is execv error: No such file or directory
before i do chmod u+x Manager-linux-x64.AppImage
./Manager-linux-x64.AppImage
Other Appimages like Davinci-Resolve newest package or Linphone are working fine, and i can open from terminal and GUI

Thats very confusing me

1 Like

Has anyone found an answer to hanny’s question yet? I’m running manjaro as well and it used to work until I upgraded to the latest download version of Manager. I get the same ‘execv error: No such file or directory’ if I run from the command line - and running from desktop menu results in nothing. Anyone can help?

Hello, i have no answer on manjaro. I have now on my laptop a dualboot with ubuntu 23.10. not my distro of choice but i can use manager accounting.
But i hope that someone can help.

1 Like

I am not an everyday user of Manjaro (or indeed any Arch based distro for that matter).
However, I was having a bit of a play earlier today and can reproduce the issue on Manjaro.
My solution to the issue was to install Distrobox and run the appimage from within an Ubuntu environment - - - worked a treat…
One of the nice things about using Distrobox is that everything integrates very nicely with the primary OS that is installed on the bare metal irrespective of the containerised environment being used to run an app or service etc.
Reference:-
https://distrobox.it/

Hi itś not a solution but a very nice idea to bypass the problem.
Have a nice Day

1 Like

I use Fedora 38 and the latest Arch/Manjaro and have had so many issues with this software package. I’ve resorted to running the software in a ubuntu 18.10 vm to bypass all the issues. Also noted that it’s not working with appimagelauncher as well. Funny how app images are supposed to work on any Linux distribution but this software is requiring dependencies. Well VM’s work great no matter what LInux distribution you are using.

I had the same issues that many other linux users have.

Basically, launching a freshly downloaded Manager AppImage will not work getting the dreaded:

execv error: No such file or directory

Trying to inspect the AppImage to learn what went wrong, I would get

Squashfs image uses (null) compression, this version supports only xz, zlib.

Diving into the rabbit hole I came across some github issues that mentioned completely removing AppImageLauncher would resolve these problems, so I tried it, and it did.

So if you have problems launching Manager using an AppImage on Linux with one of the errors mentioned above, try uninstalling AppImageLauncher and see if that works for you:

sudo apt remove appimagelauncher

Download latest Manager AppImage and check.