Desktop app: Failed to register AppImage in system via libappimage

📱 Desktop & mobile clients
1

Running Kubuntu 24.04

Nextcloud Appimage desktop app

Up to version 3.14.3 system integration was no problem, but with that version an integration error occurred. I had hoped that version 3.15.0 would have corrected this but, no, the same problem exists. It will run as a one-off but will not integrate. The error message is:-

Failed to register AppImage in system via libappimage

Any ideas?

2

Can you try the new Appimage 3.15 and confirm if the problem persists?
https://github.com/nextcloud-releases/desktop/releases/download/v3.15.0/Nextcloud-3.15.0-x86_64.AppImage

3

Thank you for your reply. As I stated in my post, I had hoped that 3.15.0 would improve the situation but it did not, the problem still persists.

4

When trying to run an AppImage on Kubuntu 24.04, you might encounter the error: “Failed to register AppImage in system via libappimage.” This issue can have several causes and solutions:

  1. Missing FUSE library:
    AppImage files require the FUSE (Filesystem in Userspace) library to function properly. In newer Ubuntu versions, including 24.04, the required version of this library might be missing. To resolve this, install the libfuse2t64 package using the following command:

    sudo apt install libfuse2t64

    After installation, try running the AppImage file again.

  2. Incorrect file permissions:
    Ensure that the AppImage file has executable permissions. You can verify and set this as follows:

    • Right-click on the AppImage file and select “Properties.”
    • Go to the “Permissions” tab and check the option “Allow executing file as a program.”

    Alternatively, you can use the terminal:

    chmod +x /path/to/file.AppImage

  3. Issues with a specific AppImage file:
    If the issue occurs only with a particular AppImage file, the problem might lie within the file itself. Some AppImage files may have incorrect icon settings or missing dependencies, causing errors during system registration. In this case, consider contacting the app developer or looking for alternative sources for the application.

  4. Problems with AppImageLauncher:
    If you’re using AppImageLauncher to integrate AppImage files into the system and encounter this error, it could be an issue with a specific version of AppImageLauncher or its package dependencies. It’s recommended to update AppImageLauncher to the latest version or ensure that all necessary dependencies, such as libcurl3, are installed.

    (GitHub Issue Reference)

If the issue persists after performing these steps, check system logs for more details or contact the application support team.

5

Thank you for your reply.

libfuse2t64 is already the newest version. Normally, the launcher sorts out the executable requirement but I had already checked for that, besides, it does work as a one-off. There is nothing wrong with the launcher, this only occurs with the Nextcloud appimages 3.14.3 & 3.15.0. I have been using many versions of the Nextcloud appimage for a long time and these have worked with no problems.
The problem lies with the recent apps. I am surprised other people haven’t complained about this but it is possible that the majority will simply run the appimage independently and not integrate it into the system as I do.

6

It looks like the issue is specific to the newer Nextcloud AppImage versions 3.14.3 and 3.15.0, since older versions worked fine for you. Seems like something changed in how they’re packaged or work.

What could be wrong and what you can try:

  1. Changes in the AppImage package:
    The newer versions might have been updated in a way that causes issues with tools like AppImageLauncher, which handle system integration.

    What to try: Test a different integration tool, like Go AppImage, and see if it fixes the issue.

  2. Missing libraries:
    It’s possible that these newer versions need some updated system libraries that your Kubuntu doesn’t have yet.

    What to do: Try running the AppImage in the terminal and check for any errors about missing libraries. If you spot something, install the missing ones.

  3. You’re not alone:
    Other users have reported similar issues with these versions. It could just be a bug in the AppImage itself.

    What to do: Check their GitHub Issues page to see if someone else has already reported this and if there are any fixes or workarounds shared there.

Possible fixes:

  • If nothing else works, you can reach out to Nextcloud Github. They might already be working on this.
  • In the meantime, stick to an older version that worked until they release a fix.
  • If AppImageLauncher is giving you trouble, you can still run the AppImage without integrating it into your system, even though it’s less convenient.

For me personally, I use AppImages very rarely. Most of the time, I rely on the regular Nextcloud client that’s fully integrated into my system on CachyOS. Since this issue seems specific to these versions, it’s probably worth keeping an eye on updates from Nextcloud to see if they patch it.