Cryptomator AppImage Update Fails

I have not been able to upgrade past Cryptomator v1.13.0.

My desktop system is dual boot with Ubuntu 20.04 LTS as my primary desktop: Intel i7 CPU and 16GB memory.

AppImageLauncher is installed.

I think my initial Cryptomator install was v1.11.1 with upgrades to v1.12.3 and v1.13.0

I have tried to install v1.15.3, v1.16.0, and v1.17.1.

All 3 versions have similar symptoms, so I will describe the v1.17.1 experience.

• Open the desktop “Show Applications” icon (bottom left) and right click the existing Cryptomator icon and delete the existing application (v1.13.0)
• I download v1.17.1 from the Cryptomator download site:
•  https://cryptomator.org/downloads/#linux
• cryptomator-1.17.1-x86_64.Applmage
• Save the file in a Cryptomator folder. (Several older versions are in this folder)
• Checked the SHA256 signature, it matched
• Copy the file to my Ubuntu desktop and doubleclick the file to run AppImageLauncher.
• The new Cryptomator icon is added to the “Show Applications” set of icons, and the desktop file is deleted.
• I click on the Cryptomator icon, and see a small circle with moving dots, then nothing.  (I was expecting to see the Cryptomator window)
• Yet, the v1.17.1 file is in my AppImage folder in my home directory as defined in the AppImageLauncher settings.
• Checking the permissions of the file in my /home directory: Read and Write for all users, and Allow executing file as a program is checked.  Also the same permissions for the v1.13.0 file.

Every time I tried to update to a later version, I have had to revert back to v1.13.0.

My questions:
1. Am I doing something wrong?
2. Are the newer Cryptomator AppImage missing some dependencies for Ubuntu 20.04 LTS?
3. Should I try a PPA?
4. Should I try a deb file if a deb file is available?
5. Any other suggestions?

Hi,

Unfortunately it is appimagelauncher that might be the culprit. It has not been updated by the developer for a few years now. Undeveloped software is bound to catch a bug eventually.

Two thoughts,

Create a new user and log in as that user so there is no app image launcher configured for that person and then try and run the new version of the software see if it works then try using it with app image launcher without having the two previous versions installed and see if it upgrades correctly.

What if you try removing the earlier versions of software and also app image launcher reboot and then try and run first without app image launcher.

Here are instructions I got that look very accurate from chat gpt.

It is actually the culprit. Cryptomator uses a new appimage format, which is not supported by the appimage launcher (version 2.x) anymore, see cryptomator-1.15.0-x86_64.AppImage Compatibility issues with AppImageLauncher · Issue #3717 · cryptomator/cryptomator · GitHub

But it seems it is compatible with version 3.x

Thankyou LeoW and infeo for identifying the AppImageLauncher problem.

I think I have the following options

  1. Stay with Cryptomator v1.13

  2. Take the risk and install AppImageLauncher v3xx

  3. Remove AppImageLauncher and copy Cryptomator v1.17.1 to my AppImage folder and run without AppImageLauncher supports

Staying with v1.13 is not a good idea since there have been at least 4 updates. Do I want to accept the data-integrity risk using down-level code?

The 3xx version of AppImageLauncher might work, but it might not. No timeline for when the code will be in Beta or released. What is the benefit on installing AppImageLauncher versus the risk?

Removing the down-level AppImageLauncher and using the latest version of Cryptomator without the launcher seems the best option. I will lose the Cryptomator icon in the show applications menu.

The following documents provided guidance on the removal process.

“Removing appimagelauncher & apps”

By the way, the AppImageLauncher PPA is now depreciated.

THIS PPA IS DEPRECATED!

See Close PPAs? · TheAssassin/AppImageLauncher · Discussion #706 · GitHub

Migration from v1.13 to v1.17.1 question.

The vault was last updated with v.1.13.

Can I use v1.17.1 directly?

Or do I need to open the vault with v1.13, save the files to another location, then remove v1.13 and recreated the vault with v1.17.1, then move the saved files into the new vault?

Hi @j_mator_fla

There is a newer application that is actively maintained that can and will manage app images and put them into the menu.

It’s called “gear lever” and it’s a flatpak app.

I have been using this program instead of the app image launcher.

1 Like

Yes. You don’t need to copy your data toto another location

thank you linfeo, I used v1.17.1 to open my vault.