Package Details: cryptomator-bin 1.12.2-1

Git Clone URL: (read-only, click to copy)
Package Base: cryptomator-bin
Description: Multiplatform transparent client-side encryption of your files in the cloud.
Upstream URL:
Keywords: AppImage binary cryptography encryption
Licenses: GPL3
Conflicts: cryptomator
Provides: cryptomator
Replaces: cryptomator
Submitter: ajgraves
Maintainer: ajgraves (overheadhunter, SailReal)
Last Packager: SailReal
Votes: 28
Popularity: 0.96
First Submitted: 2021-05-02 19:50 (UTC)
Last Updated: 2024-02-09 12:42 (UTC)

Pinned Comments

ajgraves commented on 2021-05-02 20:00 (UTC)

Hello everyone! This is a new package, created from cryptomator which is being updated to build from source. This package will always install the latest binary (AppImage) as built from upstream. If you'd rather build the app from source, please use the cryptomator package instead.

Latest Comments

1 2 Next › Last »

SailReal commented on 2023-06-04 19:06 (UTC)

@mewsen thanks for the hint. AppImages still require Fuse2 to run. Added fuse2 as dependency.

mewsen commented on 2023-06-04 11:47 (UTC)

I had to install fuse2 to get it working.

alexounet commented on 2022-05-15 18:18 (UTC)

@SailReal: it works now, thanks. Turns out that I just had to indicate KDE Wallet as password manager (it was blank since I kept the config files from another DE). I assume that my issue was related to

SailReal commented on 2022-04-29 10:49 (UTC)

@alexounet can you please fill up a bug report containing all that information on and containing all the information you found out during the tests. Thank you :)

alexounet commented on 2022-04-27 18:29 (UTC) (edited on 2022-04-27 18:58 (UTC) by alexounet)

The latest version 1.6.9-1 works fine until I click on the GUI window to lock the vault. Then, kwin_x11 becomes unresponsive and needs to be restarted via CLI. 1.6.8 did not have this issue on my Plasma session so I rolled back to the Flatpak which is still 1.6.8.

SailReal commented on 2022-03-03 14:23 (UTC)

@purejava wow, thank you very much for the information and the upstream work in KeePassXC nailing down this problem!

purejava commented on 2022-03-02 18:26 (UTC)

@SailReal Thanks, but no. The issue you describe is logged as:

17:40:16.917 [JavaFX Application Thread] INFO  org.purejava.KeepassProxyAccess - org.purejava.KeepassProxyAccessException: ErrorCode: 1, Datenbank nicht geöffnet
17:40:31.420 [JavaFX Application Thread] INFO  org.purejava.KeepassProxyAccess - org.purejava.KeepassProxyAccessException: Error: message could not be decrypted

This is due to KeePassXC 2.6.6 sometimes having problems with messages (send between KeePassXC and a client) getting out of sync and therefore cannot be decrypted on the client side. This was noticed for a different scenario and fixed by, which fixes the issue you point out for keepassxc-cryptomator too. KeePassXC Release 2.7.0-beta1 contains the fix.

SailReal commented on 2022-03-02 11:04 (UTC)

@purejava haven't had time to look for the cause yet but what I've also noticed is this: if KeepassXC is not unlocked when you start Cryptomator, you have to restart Cryptomator first so you can unlock the vaults with passwords from KeepassXC. Maybe that was the problem you noticed.

purejava commented on 2022-03-02 06:43 (UTC)

@SailReal Thanks for testing. It's GNOME on Arch linux (VM). I could not reproduce it either. I re-tested on a different VM (GNOME on Arch linux as well) today and it worked fine. Sorry for the noise.

SailReal commented on 2022-03-01 23:00 (UTC)

@purejava what distro and DE do you use? On Manjaro using GNOME it works for me using cryptomator and cryptomator-bin