Arch Linux User Repository

Everyone, with great thanks to @SailReal, this package now builds Cryptomator from source. If you wish to continue using the binary AppImage build, you need only to install cryptomator-bin.

We made this change to better align with the desires of the community (you've asked a few times to make this a "build from source" package) as well as better align to the package naming convention within the AUR.

@Fatum maybe it is a bug can you please create an issue containing all that information on https://github.com/cryptomator/cryptomator/issues/new?assignees=&labels=type%3Abug&template=bug.yml and containing all the information you found out during the tests. Thank you :)

Hello! I have manjaro KDE latest version. I updated cryptomator to version 1.6.9. Now when selecting the storage folder for 2 minutes the program and the system hangs.

12:23:20.703 [JavaFX Application Thread] INFO o.f.dbus.handlers.SignalHandler - Await signal org.kde.KWallet$walletAsyncOpened(/modules/kwalletd5) within 120 seconds.
12:25:20.706 [JavaFX Application Thread] WARN o.f.dbus.handlers.SignalHandler - java.util.concurrent.TimeoutException

This didn't happen on the previous version. Is there any way to fix it?

@SailReal Thank you - this one is working :-)

@agarbathi gpg --keyserver keys.gnupg.net --recv-keys 58117AFA1F85B3EEC154677D615D449FE6E6A235 should help if your default keyserver doesn't have the key included. Otherwise you can also retrieve it from our Cryptobot using curl -sSL https://github.com/cryptobot.gpg | gpg --import -

:: Lade PKGBUILDs herunter… PKGBUILDs sind aktuell nichts Neues zu überprüfen :: Schlüssel müssen importiert werden:) 58117AFA1F85B3EEC154677D615D449FE6E6A235 wird gefordert von: cryptomator-1.6.7-1 :: import? [J/n]: J gpg: Empfangen vom Schlüsselserver fehlgeschlagen: Server zeigt einen unbestimmten Fehler an Fehler: Ausführung fehlgeschlagen: gpg --recv-keys 58117AFA1F85B3EEC154677D615D449FE6E6A235:

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

@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 https://github.com/keepassxreboot/keepassxc/pull/7404, which fixes the issue you point out for keepassxc-cryptomator too. KeePassXC Release 2.7.0-beta1 contains the fix.

@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.

@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.

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