Package Details: cryptomator 1.6.10-1

Git Clone URL: https://aur.archlinux.org/cryptomator.git (read-only, click to copy)
Package Base: cryptomator
Description: Multiplatform transparent client-side encryption of your files in the cloud.
Upstream URL: https://cryptomator.org/
Keywords: cryptography encryption
Licenses: GPL3
Submitter: Foxboron
Maintainer: ajgraves (overheadhunter, SailReal)
Last Packager: SailReal
Votes: 73
Popularity: 1.38
First Submitted: 2016-04-03 17:36 (UTC)
Last Updated: 2022-05-09 11:15 (UTC)

Dependencies (10)

Required by (1)

Sources (2)

Pinned Comments

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

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.

Latest Comments

SailReal commented on 2022-05-09 11:33 (UTC)

@purejava Thanks for the hint. Just applied your suggested changes :)

purejava commented on 2022-05-08 03:00 (UTC)

Java 18 is out. Building the package on a systen with Java 18 installed, it downloads the Java 17 makedependency, but the build nevertheless fails with:

==> Beginne prepare()...
You don't have a Java 17 JDK selected but the following installed on your system:
  java-17-openjdk
Select a Java 17 JDK using "sudo archlinux-java set [name from the list above]"
If you switched to a JDK 17, please re-run the installation.
==> FEHLER: Ein Fehler geschah in prepare().
    Breche ab...

This could be improved with makedepends=('java-environment>=17' 'maven') and a modified error message. I changed the message for keepassxc-cryptomator, maybe you want to take a look.

Fatum commented on 2022-05-01 14:58 (UTC)

@SailReal ok i does it

SailReal commented on 2022-05-01 11:04 (UTC)

@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 :)

Fatum commented on 2022-05-01 09:32 (UTC) (edited on 2022-05-01 09:35 (UTC) by Fatum)

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?

agarbathi commented on 2022-03-25 16:47 (UTC)

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

SailReal commented on 2022-03-24 19:02 (UTC)

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

agarbathi commented on 2022-03-24 18:55 (UTC)

:: 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:

SailReal commented on 2022-03-03 14:24 (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:28 (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 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.

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:42 (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

purejava commented on 2022-02-28 06:41 (UTC) (edited on 2022-02-28 06:41 (UTC) by purejava)

cryptomator does not read contents of the pluginDir: ~/.local/share/Cryptomator/plugins and hence not uses the keepassxc-cryptomator plugin when startet via the .desktop entry. It does use the pluginDir when startet via the CLI.

commented on 2021-12-18 14:12 (UTC)

@SailReal I rebooted and that solved the problem. Thank you very much.

SailReal commented on 2021-12-13 13:39 (UTC) (edited on 2021-12-13 13:40 (UTC) by SailReal)

@currantpigeonsty did you just installed the Java environment like e.g. jdk-openjdk? If so you need to do the following so that your environment uses the updated $PATH variable:

After installation, the Java environment will need to be recognized by the shell ($PATH variable). This can be done by sourcing /etc/profile from the command line or by logging out/in again of the Desktop Environment or reboot. (From https://wiki.archlinux.org/title/java)

After that, the installation should work :)

commented on 2021-12-13 13:14 (UTC)

I got the following error message and makepkg stopped.

PKGBUILD: line 54: jlink: command not found

Do you have dependency issues?

SailReal commented on 2021-11-18 20:10 (UTC)

@xafr there are a few packages that provide java-environment=17, some are even in the main repo like e.g. https://archlinux.org/packages/extra/x86_64/jdk-openjdk/ or the AUR has e.g. https://aur.archlinux.org/packages/zulu-17-bin/

xafr commented on 2021-11-18 19:43 (UTC)

Thanks for your hint with Java 16. Seems like the new version needs Java 17 to install which I don't even have on manjaro... "unable to satisfy dependency 'java-environment=17' required by cryptomator" Is there a way to install it without those java-dependencies?

SailReal commented on 2021-10-29 18:45 (UTC)

@Fatum v1.6.2 will be published on Monday or Tuesday with a bugfix for it. Here is the issue for more information: https://github.com/cryptomator/cryptomator/issues/1866

Fatum commented on 2021-10-29 18:38 (UTC) (edited on 2021-10-29 18:38 (UTC) by Fatum)

Please help! After updating the package, the program runs only from root. If you run it as a normal user, the GUI does not start.

(cryptomator:9280): Gtk-WARNING **: 21:26:39.908: Theme parsing error: gtk.css:73:46: The style property GtkScrolledWindow:scrollbars-within-bevel is deprecated and shouldn't be used anymore. It will be removed in a future version 21:26:40.115 [JavaFX Application Thread] INFO o.c.ui.launcher.FxApplicationStarter - JavaFX Runtime started. Exception in thread "JavaFX Application Thread" java.io.UncheckedIOException: Failed to load /fxml/main_window.fxml at org.cryptomator.desktop@1.6.1/org.cryptomator.ui.common.FxmlLoaderFactory.createScene(FxmlLoaderFactory.java:61) at org.cryptomator.desktop@1.6.1/org.cryptomator.ui.common.FxmlLoaderFactory.createScene(FxmlLoaderFactory.java:47) at org.cryptomator.desktop@1.6.1/org.cryptomator.ui.mainwindow.MainWindowModule.provideMainScene(MainWindowModule.java:76) at org.cryptomator.desktop@1.6.1/org.cryptomator.ui.mainwindow.MainWindowModule_ProvideMainSceneFactory.provideMainScene(MainWindowModule_ProvideMainSceneFactory.java:31) at org.cryptomator.desktop@1.6.1/org.cryptomator.launcher.DaggerCryptomatorComponent$MainWindowComponentImpl.fxmlSceneScene(DaggerCryptomatorComponent.java:5933) at org.cryptomator.desktop@1.6.1/org.cryptomator.launcher.DaggerCryptomatorComponent$MainWindowComponentImpl$SwitchingProvider.get(DaggerCryptomatorComponent.java:6062) at dagger@2.39/dagger.internal.DoubleCheck.get(DoubleCheck.java:47) at org.cryptomator.desktop@1.6.1/org.cryptomator.ui.mainwindow.MainWindowComponent.showMainWindow(MainWindowComponent.java:28) at org.cryptomator.desktop@1.6.1/org.cryptomator.ui.fxapp.FxApplication.lambda$showMainWindow$1(FxApplication.java:114) at javafx.graphics/com.sun.javafx.application.PlatformImpl.lambda$runLater$10(PlatformImpl.java:457) at java.base/java.security.AccessController.doPrivileged(Unknown Source) at javafx.graphics/com.sun.javafx.application.PlatformImpl.lambda$runLater$11(PlatformImpl.java:456) at javafx.graphics/com.sun.glass.ui.InvokeLaterDispatcher$Future.run(InvokeLaterDispatcher.java:96) at javafx.graphics/com.sun.glass.ui.gtk.GtkApplication._runLoop(Native Method) at javafx.graphics/com.sun.glass.ui.gtk.GtkApplication.lambda$runLoop$11(GtkApplication.java:290) at java.base/java.lang.Thread.run(Unknown Source)

full code error: http://pastie.org/p/4zCTHXasb8FrlW026OpPko

SailReal commented on 2021-09-23 18:35 (UTC)

@xafr and @aquatic7 please make sure, that you use java version 16 to build the project. You can check with archlinux-java status which one is selected (marked with default) and use e.g. sudo archlinux-java set zulu-16 to set it. After setting java 16 you should be able to build and install this package.

aquatic7 commented on 2021-09-23 16:04 (UTC)

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project commons: Fatal error compiling: invalid flag: --release -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn <args> -rf :commons ==> ERROR: A failure occurred in build(). Aborting...

xafr commented on 2021-09-16 18:04 (UTC)

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project commons: Fatal error compiling: invalid flag: --release -> [Help 1] [ERROR]

ajgraves commented on 2021-07-09 21:10 (UTC)

The latest release on Linux is 1.5.15, which is the version of this package. For the person who flagged it out of date because 1.5.16 exists, if you look at that package it was a hotfix for Windows only, and as such, no 1.5.16 was released for the Linux platform.

dr460nf1r3 commented on 2021-07-04 11:37 (UTC)

@peterlewis: the hint about adding to $PATH did the trick, thanks! :)

peterlewis commented on 2021-07-04 11:27 (UTC) (edited on 2021-07-04 11:28 (UTC) by peterlewis)

@dr460nf1r3 It's my experience that neither /usr/lib/jvm/default/bin or /usr/lib/jvm/default-runtime/bin get added to your $PATH. I successfully installed cryptomator as follows:

  1. Install zulu-16-bin or amazon-corretto-16
  2. sudo archlinux-java set zulu-16 or amazon-corretto-16
  3. PATH=/usr/lib/jvm/default/bin:$PATH
  4. Install cryptomator from AUR

SailReal commented on 2021-07-03 17:24 (UTC) (edited on 2021-07-03 17:24 (UTC) by SailReal)

@dr460nf1r3 if you install something like zulu-16-bin, jlink comes with it and should be available. Maybe a rebooted is required after the first install of java? What does which jlink and whereis jlink prints out?

dr460nf1r3 commented on 2021-07-03 14:53 (UTC)

This seems to need jlink as makedepend as makepkg fails due to this one missing when building in clean chroot. However, even if this is installed it still fails with the same error message. Complete logs are available.

SailReal commented on 2021-05-25 15:37 (UTC)

@cirlo Sorry for the confusion from my side. While testing this issue, I did a lot of changes on my system to find out the cause of it. While testing I stumbled over https://github.com/cryptomator/cryptomator/issues/1663 and unfortunately, I also switched from Fuse to WebDAV which actually fixes this force unlock problem.

So this problem still exists when using Fuse but for https://github.com/cryptomator/cryptomator/issues/1663, as you said, use e.g. zulu-16-bin or amazon-corretto-16 to build this project.

cirlo commented on 2021-05-20 11:37 (UTC) (edited on 2021-05-20 11:37 (UTC) by cirlo)

@SailReal once again came and solved the issue (https://github.com/cryptomator/cryptomator/issues/1658): make sure to use zulu-16-bin or amazon-corretto-16. With jdk-adoptopenjdk or aur/jdk you will encounter problems when trying to lock the vault.

cirlo commented on 2021-05-19 16:17 (UTC)

@SailReal thank you very much! Both for the fast reply and the issue you opened upstream

SailReal commented on 2021-05-19 16:14 (UTC)

@cirlo no but I can reproduce it, just created this issue: https://github.com/cryptomator/cryptomator/issues/1658

cirlo commented on 2021-05-19 15:38 (UTC)

Does it ever happen to you that, after unlocking, mounting and using, you can't lock the drive back? Even if i try to force the locking, it throws org.cryptomator.common.vaults.LockNotCompletedException

Kreba commented on 2021-05-03 15:52 (UTC) (edited on 2021-05-03 15:58 (UTC) by Kreba)

$ archlinux-java status
Available Java environments:
java-16-adoptopenjdk
java-8-openjdk (default)
$ sudo archlinux-java set java-16-openjdk
...
'/usr/lib/jvm/java-16-openjdk' is not a valid Java environment path
$ sudo archlinux-java set java-16-adoptopenjdk
$ archlinux-java status
Available Java environments:
java-16-adoptopenjdk (default)
java-8-openjdk

Thanks!

KoaTravis commented on 2021-05-03 12:13 (UTC) (edited on 2021-05-03 12:15 (UTC) by KoaTravis)

@Kreba Try to set the active java installation using the archlinux-java script. List the available java environments with:
archlinux-java status
And set it with:
archlinux-java set java-16-openjdk

Kreba commented on 2021-05-03 11:44 (UTC) (edited on 2021-05-03 11:47 (UTC) by Kreba)

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project commons: Fatal error compiling: invalid flag: --release -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn <args> -rf :commons

insalled: jdk-adoptopenjdk 16.0.1.u9-1 jdk8-openjdk 8.u292-1 jre8-openjdk 8.u292-1 jre8-openjdk-headless 8.u292-1

SailReal commented on 2021-05-03 07:54 (UTC)

@Achilleus which Java package did you installed? It looks like it is just a runtime and not the development kit with a compiler. Just to mention two random packages which should work: https://aur.archlinux.org/packages/jdk/, https://aur.archlinux.org/packages/jdk-adoptopenjdk/

Achilleus commented on 2021-05-03 07:46 (UTC)

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project commons: Compilation failure [ERROR] No compiler is provided in this environment. Perhaps you are running on a JRE rather than a JDK? [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn <args> -rf :commons

Dwa30v commented on 2021-05-03 07:23 (UTC)

@sToRmInG - Thanks!

sToRmInG commented on 2021-05-03 07:04 (UTC)

@Dwa30v You have to have OpenJDK 16 installed. Currently there is no JDK 16 available in the official repo so you'll have to use one from AUR.

Dwa30v commented on 2021-05-03 04:24 (UTC)

Error: Failed to prepare transaction:
could not satisfy dependencies:
- unable to satisfy dependency 'java-environment=16' required by cryptomator

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

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.

Kreba commented on 2021-02-25 15:09 (UTC)

Erneuere cryptomator (1.5.12-2 -> 1.5.13-2)... Vorgang erfolgreich abgeschlossen.

Danke! - Thank you

ajgraves commented on 2021-02-25 14:14 (UTC)

All who reported checksum issues, the checksum I got matched when the new version was released. It appears this is the second time that upstream has updated the package without bumping the version, causing a checksum mismatch. Give me a few minutes and I'll have this updated.

commented on 2021-02-25 14:13 (UTC)

Not sure where you're getting the sha256sum from, but the one in your PKGBUILD for the appimage causes the build to fail, where the one listed on https://cryptomator.org/downloads/linux/thanks/ works fine for me.

commented on 2021-02-25 14:11 (UTC)

Not sure where you're getting the sha256sum from for the latest release, but the one listed on https://cryptomator.org/downloads/linux/thanks/ works fine for me where as the one in your PKGBUILD doesn't.

Kreba commented on 2021-02-25 13:03 (UTC)

Erstelle cryptomator... ==> Erstelle Paket: cryptomator 1.5.13-1 (Do 25 Feb 2021 14:01:47 CET) ==> Prüfe Laufzeit-Abhängigkeiten... ==> Prüfe Buildtime-Abhängigkeiten... ==> Empfange Quellen... -> cryptomator-1.5.13-1-x86_64.AppImage gefunden -> org.cryptomator.Cryptomator.desktop gefunden -> org.cryptomator.Cryptomator.png gefunden -> org.cryptomator.Cryptomator.svg gefunden -> cryptomator-vault.xml gefunden ==> Überprüfe source Dateien mit sha256sums... cryptomator-1.5.13-1-x86_64.AppImage ... FEHLGESCHLAGEN org.cryptomator.Cryptomator.desktop ... Durchgelaufen org.cryptomator.Cryptomator.png ... Durchgelaufen org.cryptomator.Cryptomator.svg ... Durchgelaufen cryptomator-vault.xml ... Durchgelaufen ==> FEHLER: Eine oder mehrere Dateien überstanden nicht die Gültigkeits-Prüfung! Fehler beim Erstellen von cryptomator

Viele Grüße und Danke!

plgonzalezrx8 commented on 2021-02-25 12:57 (UTC) (edited on 2021-02-25 13:12 (UTC) by plgonzalezrx8)

Same error as last time. It doesn't pass the validity check.

==> Validating source files with sha256sums...
    cryptomator-1.5.13-1-x86_64.AppImage ... FAILED
==> ERROR: One or more files did not pass the validity check!
Failed to build cryptomator

Dwa30v commented on 2021-02-20 13:08 (UTC)

@ajgraves, thanks a lot!

ajgraves commented on 2021-02-20 12:41 (UTC)

@Dwa30v, it appears the package was updated by upstream without bumping the version number, so the checksum changed. I have pushed an update to the PKGBUILD to fix that.

Dwa30v commented on 2021-02-20 11:57 (UTC) (edited on 2021-02-20 11:57 (UTC) by Dwa30v)

==> Validating source files with sha256sums...
    cryptomator-1.5.12-x86_64.AppImage ... FAILED
==> ERROR: One or more files did not pass the validity check!
Failed to build cryptomator

commented on 2020-10-05 13:51 (UTC)

This software is open source software. However, PKGBUILD uses binaries. The correct package name is cryptomator-bin.

commented on 2020-10-05 13:46 (UTC)

java-openjfx should be added to the dependent packages.

exoro commented on 2020-06-28 20:43 (UTC)

Thanks, pete_mitchell! Just want to make a correction to your typo though. The package that fixes the issue is java-openjfx

pete_mitchell commented on 2020-04-22 05:39 (UTC) (edited on 2020-04-22 06:06 (UTC) by pete_mitchell)

UPDATE: Issue fixed
By running the AppImage from terminal, I noticed it was calling OpenJFX (rather than OpenJDK). I installed OpenJDK and now this package is working!


Issue
I've built and installed successfully but the app wont launch... complaining about Java:

15:13:33.136 [main] INFO  org.cryptomator.launcher.Cryptomator - Starting Cryptomator 1.5.0 on Linux 5.4.33-3-lts (amd64)
Exception in thread "main" java.lang.UnsupportedOperationException: Desktop API is not supported on the current platform
        at java.desktop/java.awt.Desktop.getDesktop(Desktop.java:303)
        at org.cryptomator.ui.launcher.AppLifecycleListener.<init>(AppLifecycleListener.java:47)
        at org.cryptomator.ui.launcher.AppLifecycleListener_Factory.newInstance(AppLifecycleListener_Factory.java:51)
        at org.cryptomator.ui.launcher.AppLifecycleListener_Factory.get(AppLifecycleListener_Factory.java:39)
        at org.cryptomator.ui.launcher.AppLifecycleListener_Factory.get(AppLifecycleListener_Factory.java:11)
        at dagger.internal.DoubleCheck.get(DoubleCheck.java:47)
        at org.cryptomator.ui.traymenu.TrayMenuController_Factory.get(TrayMenuController_Factory.java:41)
        at org.cryptomator.ui.traymenu.TrayMenuController_Factory.get(TrayMenuController_Factory.java:12)
        at dagger.internal.DoubleCheck.get(DoubleCheck.java:47)
        at org.cryptomator.ui.traymenu.TrayIconController_Factory.get(TrayIconController_Factory.java:34)
        at org.cryptomator.ui.traymenu.TrayIconController_Factory.get(TrayIconController_Factory.java:9)
        at dagger.internal.DoubleCheck.get(DoubleCheck.java:47)
        at org.cryptomator.launcher.DaggerCryptomatorComponent$TrayMenuComponentImpl.trayIconController(DaggerCryptomatorComponent.java:677)
        at org.cryptomator.ui.traymenu.TrayMenuComponent.addIconToSystemTray(TrayMenuComponent.java:20)
        at org.cryptomator.ui.launcher.UiLauncher.launch(UiLauncher.java:47)
        at org.cryptomator.launcher.Cryptomator.runGuiApplication(Cryptomator.java:91)
        at org.cryptomator.launcher.Cryptomator.run(Cryptomator.java:75)
        at org.cryptomator.launcher.Cryptomator.main(Cryptomator.java:48)
Cryptomator Failed to launch JVM

I tried the following:

  1. Installed 2 JREs - refer code block at bottom
  2. Disabled firewall (ufw)
  3. Downloaded the AppImage from upstream and it executed successfully.
$ archlinux-java status
Available Java environments:
  java-11-openjdk
  java-13-openjdk (default)

Switched to both Java versions.

matthias.lisin commented on 2020-01-26 22:34 (UTC)

@ajgraves That's the reason :P makepkg doesn't install dependencies by default.

-s, --syncdeps   Install missing dependencies with pacman

ajgraves commented on 2020-01-26 21:47 (UTC)

@matthias.lisin I am not, I'm running just regular makepkg

matthias.lisin commented on 2020-01-26 10:29 (UTC)

@ajgaves Are you running makepkg with the -s flag?

ajgraves commented on 2020-01-25 20:28 (UTC)

@matthias.lisin probably because I already had jdk13 installed. The makepkg command errored out complaining about needing jdk=11.

It may not be uncommon for others to have multiple versions installed (but I could be wrong about that?)

matthias.lisin commented on 2020-01-25 19:31 (UTC)

@ajgraves weird. makedepends has java-environment-openjdk=11 so makepkg should install it for you.

How are you building the package?

ajgraves commented on 2020-01-25 18:36 (UTC)

@matthias.lisin built your latest package, installed and tested briefly. Seems to do well. I had to install jdk11 before hand though.

test0 commented on 2020-01-24 19:04 (UTC) (edited on 2020-01-24 19:06 (UTC) by test0)

I've submitted two pull requests on GitHub:
https://github.com/cryptomator/cryptomator-linux/pull/20
https://github.com/cryptomator/docker/pull/4
To fix the following issue:
https://github.com/cryptomator/cryptomator/issues/956
They were merged in the repositories for the PPA and AppImage builds, so this is the last repository where the fix needs to be applied.

The following changes since commit 53350fec42bcf94072d82a97dff004de97a64560:

  Update to 1.4.15 (2019-08-18 16:36:53 +0200)

are available in the Git repository at:

  https://github.com/giovannivelludo/aur-cryptomator.git master

for you to fetch changes up to b27501ee8c7bc3b99fc65de76985420f8866492a:

  Added missing StartupWMClass (2020-01-24 19:36:56 +0100)

----------------------------------------------------------------
giovannivelludo (1):
      Added missing StartupWMClass

 cryptomator.desktop | 1 +
 1 file changed, 1 insertion(+)

diff --git a/cryptomator.desktop b/cryptomator.desktop
index cc74bb5..39068e7 100644
--- a/cryptomator.desktop
+++ b/cryptomator.desktop
@@ -7,3 +7,4 @@ Terminal=false
 Type=Application
 Categories=Utility
 MimeType=application/x-vnd.cryptomator-vault-metadata
+StartupWMClass=org.cryptomator.launcher.Cryptomator$MainApp

matthias.lisin commented on 2020-01-19 13:23 (UTC)

I updated my "from-source" package: https://codeberg.org/ml/cryptomator/src/branch/source

  • uses Java 11 as recommended by upstream
  • applies upstream patch to force https for jcenter (broken otherwise)
  • explicitly request openjdk jdk/jre because a fixed path is used in wrapper script

ajgraves commented on 2019-12-31 00:41 (UTC)

@paulwaldmann no worries at all! We're actually collaborating on switching this up to a "build from source" package, so technically we'd pull down whatever the latest version in the git repo is, in this case 1.4.17.

ajgraves commented on 2019-12-31 00:40 (UTC)

Hello @matthias.lisin, apologies for the delay. I'm looking at this now, and cloned your git repo and was able to successfully build the package. I'd feel better if @overheadhunter gave it a look over as well, as I'm not the strongest at Java. It seems to have worked ok as far as I can tell.

commented on 2019-12-30 12:14 (UTC)

@ajgraves, I realized that just now, even opened an issue on Github and shortly after reading that the 1.4.16 and 1.4.17 were hotfixes for macOS users only. Once again, apologies for the confusion.

ajgraves commented on 2019-12-30 11:59 (UTC)

I unflagged this package as being out of date, as the latest AppImage version available from upstream is 1.4.15. Version 1.4.17 is only available on the Mac platform.

matthias.lisin commented on 2019-12-07 14:37 (UTC)

Hello @ajgraves and @overheadhunter, I have mailed you my build-from-source proposal two weeks ago. Didn't get any reply.

Here is my proposal in a codeberg.org git repo: https://codeberg.org/ml/cryptomator/commit/65b5bb50ead25c1209e1e1186a57a1c2caf47d39

It would be nice if anyone could review it and give me some feedback.

ajgraves commented on 2019-11-22 04:27 (UTC)

@matthias.lisin, evaluations of doing so are being made.

matthias.lisin commented on 2019-11-16 01:51 (UTC)

Can you rename this package to cryptomator-bin or build the application from source?

davidpblcrd commented on 2019-10-12 08:53 (UTC)

@ajgraves I added _JAVA_OPTIONS: -Dawt.useSystemAAFontSettings=default to my /etc/enviroment file and it worked. I'm using mainline Arch with XFCE. Thanks

ajgraves commented on 2019-10-11 23:06 (UTC)

@davidpblcrd, check this forum post that may be helpful: https://bbs.archlinux.org/viewtopic.php?id=248524

Aside from that, as all this package does is installs/runs the AppImage provided by Cryptomator, then you'd need to open an issue upstream at https://github.com/cryptomator/cryptomator/issues

What DE/WM are you running? Is this on mainline Arch or on an Arch derivative?

davidpblcrd commented on 2019-10-11 17:45 (UTC)

I get this error when I try to open the program: https://privatebin.net/?f2c20cd6cb33a797#3hqqHUfDrh7VWPuFbA4d11BzA9aNBZ8CaT1APnK1n852 I tried to install java-openjfx because I thought that the issue was with JavaFX fonts but it didn`t work.

sseneca commented on 2019-09-09 22:43 (UTC)

I've re-written the PKGBUILD to avoid the use of an AppImage and build from source instead, which is of course preferable.

Check it out here: https://gitlab.com/sseneca/cryptomator-pkgbuild/tree/master

internetuser commented on 2019-04-28 02:21 (UTC)

@FlyingJay1 Well, it downloads the AppImage from their website(I think), and their website links to this AUR page so I think you can probably trust that this is the official AppImage that gets installed. If it makes you feel any better, you can download the AppImage from their website, which is probably the same thing anyways.

FlyingJay1 commented on 2019-04-28 00:46 (UTC)

Is this some kind of a joke?

You download some binary blob from somewhere, built by who knows who, and call it a security software? It should be built from source, otherwise how can anybody trust that it does what it says it does?

mirolPirol commented on 2019-03-04 14:16 (UTC)

Cryptomator wird dringend gebraucht! Wann kommt v 1.5 für Linux? Cryptomator is very highly needed - when will v 1.5 be available

tobihagemann commented on 2019-01-20 09:32 (UTC) (edited on 2019-01-20 09:33 (UTC) by tobihagemann)

For anyone stumbling upon this comment: I unflagged the "out-of-date" status because 1.4.2 is a Windows-only hotfix. Currently, 1.4.1 is the most recent version for Linux.

ivand commented on 2018-09-25 16:56 (UTC)

Hey, could you fix the cryptomator startup script (/usr/bin/cryptomator) to use the same java version as is set in path?

Until 1.4 is out, it doesn't work if your default java on the system is higher than java-8

To fix this, replace the following lines:

export PATH="/usr/lib/jvm/java-8-openjdk/jre/bin/:$PATH"
exec /usr/bin/java \

with

export PATH="/usr/lib/jvm/java-8-openjdk/jre/bin/:$PATH"
exec /usr/lib/jvm/java-8-openjdk/jre/bin/java \

or better

with

javapath=/usr/lib/jvm/java-8-openjdk/jre/bin/
export PATH="$javapath:$PATH"
exec $javapath/java \

binaryanomaly commented on 2018-09-03 15:42 (UTC)

According to the discussions in the openjfx bug the missing gtk2 dependency should be added to the cryptomator package. (Since openjfx itself does not need to be dependent on gtk2 to function).

binaryanomaly commented on 2018-09-02 08:49 (UTC)

Thanks fawn. I opened a bug over here https://bugs.archlinux.org/task/59904 so java-openjfx maintainers can check if there's something wrong. The Wiki page mentions the dependency but I don't see it when I do "pacman -Qii java-openjfx".

fawn commented on 2018-09-02 08:18 (UTC)

To: binaryanomaly. You're right. According this thread https://bugs.openjdk.java.net/browse/JDK-8120519 GTK 2.18 or greater is required to run JavaFX. Java-openjfx package should have gtk2 as dependency.

binaryanomaly commented on 2018-09-01 21:04 (UTC)

Hmm, "sudo pacman -S gtk2" fixed it. Am I wrong to suspect that this might be a missing dependency?

fawn commented on 2018-09-01 20:08 (UTC)

This error is java-openjfx related. Check if You have multiple versions of JDK/JRE installed.

binaryanomaly commented on 2018-09-01 15:32 (UTC)

@fawn: Thanks for your feedback.

I did indeed initially choose by mistake openjdk10. Then removed cryptomator with "pacman -Rcsn cryptomator", deleted the cloned dir, cloned again and re-installed it with "makepkg -si" but still have the same error.

Any ideas how this could be fixed? Re-installing the whole system from scratch would be a lot of effort.

fawn commented on 2018-09-01 15:14 (UTC)

To: binaryanomaly

For me, it's working with openjdk8 not with openjdk10.

binaryanomaly commented on 2018-08-27 16:29 (UTC)

I'm stuck with the below error message. Any idea what went wrong?

18:22:56.362 [main] [INFO ] org.cryptomator.launcher.Cryptomator - Starting Cryptomator 1.3.5 on Linux 4.18.5-arch1-1-ARCH (amd64) Graphics Device initialization failed for : es2, sw Error initializing QuantumRenderer: no suitable pipeline found java.lang.RuntimeException: java.lang.RuntimeException: Error initializing QuantumRenderer: no suitable pipeline found at com.sun.javafx.tk.quantum.QuantumRenderer.getInstance(QuantumRenderer.java:280) at com.sun.javafx.tk.quantum.QuantumToolkit.init(QuantumToolkit.java:221) at com.sun.javafx.tk.Toolkit.getToolkit(Toolkit.java:248) at com.sun.javafx.application.PlatformImpl.startup(PlatformImpl.java:209) at com.sun.javafx.application.LauncherImpl.startToolkit(LauncherImpl.java:675) at com.sun.javafx.application.LauncherImpl.launchApplication1(LauncherImpl.java:695) at com.sun.javafx.application.LauncherImpl.lambda$launchApplication$1(LauncherImpl.java:182) at java.lang.Thread.run(Thread.java:748) Caused by: java.lang.RuntimeException: Error initializing QuantumRenderer: no suitable pipeline found at com.sun.javafx.tk.quantum.QuantumRenderer$PipelineRunnable.init(QuantumRenderer.java:94) at com.sun.javafx.tk.quantum.QuantumRenderer$PipelineRunnable.run(QuantumRenderer.java:124) ... 1 more Exception in thread "main" java.lang.RuntimeException: No toolkit found at com.sun.javafx.tk.Toolkit.getToolkit(Toolkit.java:260) at com.sun.javafx.application.PlatformImpl.startup(PlatformImpl.java:209) at com.sun.javafx.application.LauncherImpl.startToolkit(LauncherImpl.java:675) at com.sun.javafx.application.LauncherImpl.launchApplication1(LauncherImpl.java:695) at com.sun.javafx.application.LauncherImpl.lambda$launchApplication$1(LauncherImpl.java:182) at java.lang.Thread.run(Thread.java:748) 18:22:56.459 [Thread-1] [INFO ] o.c.launcher.CleanShutdownPerformer - Goodbye.

veras commented on 2018-05-12 06:05 (UTC)

Will this be updated to 1.4.0 Beta 1? https://github.com/cryptomator/cryptomator/releases/tag/1.4.0-beta1

veras commented on 2018-03-17 23:27 (UTC)

The command "sudo archlinux-java set java-8-openjdk/jre" which changes the default java environment.

mirolPirol commented on 2018-03-17 12:43 (UTC)

Cryptomator dooes't start on Archmerge. I did it install with AUR-Helper "packer". Errormessage:

[micha@ArcoLENOVO ~]$ cryptomator Exception in thread "main" java.lang.UnsupportedClassVersionError: org/cryptomator/launcher/Cryptomator : Unsupported major.minor version 52.0 at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:803) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) at java.net.URLClassLoader.defineClass(URLClassLoader.java:442) at java.net.URLClassLoader.access$100(URLClassLoader.java:64) at java.net.URLClassLoader$1.run(URLClassLoader.java:354) at java.net.URLClassLoader$1.run(URLClassLoader.java:348) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:347) at java.lang.ClassLoader.loadClass(ClassLoader.java:425) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:312) at java.lang.ClassLoader.loadClass(ClassLoader.java:358) at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:482) [micha@ArcoLENOVO ~]$

What can I do to use this tool?

Slutty commented on 2018-01-21 00:41 (UTC) (edited on 2018-01-21 00:46 (UTC) by Slutty)

This package is NOT out of date. Version 1.3.3 was a "Hotfix release for Windows users...." https://github.com/cryptomator/cryptomator/releases/tag/1.3.3

Version 1.3.2 is the current latest as of writing. https://cryptomator.org/downloads/#linuxDownload

Foxboron commented on 2017-09-06 10:45 (UTC)

Nope, i was wrong. Fixed now sorry.

commented on 2017-09-06 10:41 (UTC)

Validating source files with sha256sums... cryptomator.sh ... FAILED ERROR: One or more files did not pass the validity check!

Foxboron commented on 2017-09-06 10:18 (UTC)

Sorry for that, it has been fixed. .SRCINFO is used by aurweb to display thje information on the page. It's not used by makepkg at all. Pacaur incorrectly uses this for some of the operations, it's a common complaint.

commented on 2017-09-06 10:13 (UTC)

No Problem. Another issue though: I don't understand the difference between PKGBUILD and .SRCINFO, but the PKGBUILD has the wrong checksum for cryptomator.sh, so pacaur fails at source files validation.

Foxboron commented on 2017-09-04 11:24 (UTC)

Yes, been fixing my PKGBUILDs and i overlooked the glob there. Fixed now! Sorry :)

commented on 2017-09-04 11:13 (UTC)

I don't understand why, but with the latest version I get a packaging error: install: cannot stat '/home/user/.cache/makepkg/cryptomator/src/libs/*.jar': No such file or directory Edit: I guess, bash doesn't expand the * because it's in quotation marks.

StraxKvar commented on 2017-07-03 21:27 (UTC)

Out of date. We're on version 1.3 now, which is a major re-write. Please update.

humbug commented on 2016-11-15 11:07 (UTC) (edited on 2016-11-15 13:39 (UTC) by humbug)

Edit: Okay I installed pacman -S java-openjfx as mentioned before. Maybe this should be added to dependencies ----- I get the following error: Unable to locate tools.jar. Expected to find it in /usr/lib/jvm/java-8-openjdk/lib/tools.jar Buildfile: /tmp/yaourt-tmp-niklas/aur-cryptomator/src/build.xml [taskdef] Could not load definitions from resource com/sun/javafx/tools/ant/antlib.xml. It could not be found. I am using Manjaro i3 16.10

Foxboron commented on 2016-11-13 12:58 (UTC)

Updated the hash and the make dependency as noted earlier. Also fixed the .install file

niklas.heer commented on 2016-11-13 10:34 (UTC)

The new checksum for cryptomator.sh is "c4c69b9e364469e7f1fa95fa2acaac269fb9ae18a5b9ff606b47511935a58cfc"

mgd commented on 2016-11-12 17:25 (UTC) (edited on 2016-11-12 17:25 (UTC) by mgd)

checksum check for cryptomator.sh fails with 1.2.2-1. Please fix

commented on 2016-10-23 14:07 (UTC)

Cryptomator was updated to v 1.2.0. AUR package was already flagged out of date on Sep.23. Any chance we will get an update to the latest version? I have no experience in building packages, otherwise I would do it on my own. Nevermind, I already succeeded in updating cryptomator. I just edited the PKGBUILD to the latest version and installed the necessary dependencies on my machine, after that making the package and installing the update with pacman worked flawlessly.

dschense commented on 2016-10-13 15:20 (UTC) (edited on 2016-10-13 15:37 (UTC) by dschense)

FIXED: java-openjfx was not installed.. Its not in the dependencies. just: $ pacman -S java-openjfx and then everything went fine. --------------------------------- Why do i get this error with yaourt? Buildfile: /tmp/yaourt-tmp-dschense/aur-cryptomator/src/build.xml [taskdef] Could not load definitions from resource com/sun/javafx/tools/ant/antlib.xml. It could not be found. BUILD FAILED /tmp/yaourt-tmp-dschense/aur-cryptomator/src/build.xml:6: Problem: failed to create task or type javafx:com.sun.javafx.tools.ant:application Cause: The name is undefined. Action: Check the spelling. Action: Check that any custom tasks/types have been declared. Action: Check that any <presetdef>/<macrodef> declarations have taken place. No types or tasks have been defined in this namespace yet

StraxKvar commented on 2016-09-18 19:43 (UTC)

Apologies for the constant updating, but perhaps it will help someone: I found that the problem is with how Cryptomator talks to Dolphin (the KDE file manager). I found that everything works as expected with Thunar, which is the XFCE file manager.

StraxKvar commented on 2016-09-18 19:36 (UTC)

I should add some details, perhaps: Cryptomator 1.1.4 (taken from AUR via Octopi) Linux 4.4.20 Plasma 5.7.4 Dolphin 16.08.1 jdk8-openjdk 8.u102-1 apache-ant 1.9.7 Additionally: I have tried to uninstall/restart/re-install. Problem persists. The problem is also present with newly created vaults: Can't put anything in them. I get either the same error message, as below, or no error message at all, even if the newly created vault is on a separate HD, or USB. Is it something to do with dav?

StraxKvar commented on 2016-09-18 19:28 (UTC)

Using this on Manjaro with KDE Plasma (which is Arch under the hood, essentially). No problem until yesterday. I open a vault as normal. I can read all the files in it, but I cannot write a new file into that vault (e.g. paste a photo). I get the error message "Cannot write. Disk full." (The disk is not full.) Is there something I should do to fix this? Anyone else experiencing the same problem?

suawekk commented on 2016-09-05 09:28 (UTC) (edited on 2016-09-05 09:29 (UTC) by suawekk)

Hello, Would you kindly update PKGBUILD to use "makedepends=('java-runtime-openjdk=8' 'apache-ant')" instead of "makedepends=('jdk8-openjdk' 'apache-ant')" That way cryptomator package will build under modifications of jdk-openjdk which provide OpenJDK 8 e.g. `jdk-openjdk-infinality`

alienos commented on 2016-08-16 18:00 (UTC)

Eats ram firmly until the computer slows down. I have 8GB ram.

Foxboron commented on 2016-05-03 17:18 (UTC)

Jepz. I do have adding icons and launcher on my todo!

gregor20sw commented on 2016-05-03 17:10 (UTC)

xxxx@xxxx-archbook ~]$ archlinux-java status Available Java environments: java-7-openjdk java-8-openjdk/jre (default) [xxxx@xxxx-archbook ~]$ cryptomator ERROR StatusLogger Unrecognized format specifier [d] ERROR StatusLogger Unrecognized conversion specifier [d] starting at position 16 in conversion pattern. ERROR StatusLogger Unrecognized format specifier [thread] ERROR StatusLogger Unrecognized conversion specifier [thread] starting at position 25 in conversion pattern. ERROR StatusLogger Unrecognized format specifier [level] ERROR StatusLogger Unrecognized conversion specifier [level] starting at position 35 in conversion pattern. ERROR StatusLogger Unrecognized format specifier [logger] ERROR StatusLogger Unrecognized conversion specifier [logger] starting at position 47 in conversion pattern. ERROR StatusLogger Unrecognized format specifier [msg] ERROR StatusLogger Unrecognized conversion specifier [msg] starting at position 54 in conversion pattern. ERROR StatusLogger Unrecognized format specifier [n] ERROR StatusLogger Unrecognized conversion specifier [n] starting at position 56 in conversion pattern. ERROR StatusLogger No log4j2 configuration file found. Using default configuration: logging only errors to the console. ERROR StatusLogger Unrecognized format specifier [d] ERROR StatusLogger Unrecognized conversion specifier [d] starting at position 16 in conversion pattern. ERROR StatusLogger Unrecognized format specifier [thread] ERROR StatusLogger Unrecognized conversion specifier [thread] starting at position 25 in conversion pattern. ERROR StatusLogger Unrecognized format specifier [level] ERROR StatusLogger Unrecognized conversion specifier [level] starting at position 35 in conversion pattern. ERROR StatusLogger Unrecognized format specifier [logger] ERROR StatusLogger Unrecognized conversion specifier [logger] starting at position 47 in conversion pattern. ERROR StatusLogger Unrecognized format specifier [msg] ERROR StatusLogger Unrecognized conversion specifier [msg] starting at position 54 in conversion pattern. ERROR StatusLogger Unrecognized format specifier [n] ERROR StatusLogger Unrecognized conversion specifier [n] starting at position 56 in conversion pattern. and cryptomator start, but without icons. I just find it terminal

Foxboron commented on 2016-05-03 16:20 (UTC)

I believe this error might be tied too wrong Java version. Try running archlinux-java and choose Java8. If that's that not the case i will look into it.

gregor20sw commented on 2016-05-03 16:10 (UTC)

when I launch cryptomator it says this and doen't open: [xxxxx@xxxx-archbook ~]$ cryptomator Exception in thread "main" java.lang.UnsupportedClassVersionError: org/cryptomator/ui/Cryptomator : Unsupported major.minor version 52.0 at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:803) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) at java.net.URLClassLoader.defineClass(URLClassLoader.java:449) at java.net.URLClassLoader.access$100(URLClassLoader.java:71) at java.net.URLClassLoader$1.run(URLClassLoader.java:361) at java.net.URLClassLoader$1.run(URLClassLoader.java:355) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:354) at java.lang.ClassLoader.loadClass(ClassLoader.java:425) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) at java.lang.ClassLoader.loadClass(ClassLoader.java:358) at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:482)

FillFeile commented on 2016-04-14 16:27 (UTC)

Maybe add 'rng-tools' or an other entropy generator as optinal dependency to help users with this issue: https://github.com/cryptomator/cryptomator/issues/174 Cryptomator will fall in an unresponsive state if there is not enough entropy.