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.

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

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.

@SailReal ok i does it

@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

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.

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

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

I got the following error message and makepkg stopped.

PKGBUILD: line 54: jlink: command not found

Do you have dependency issues?

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

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?

@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

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

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

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

[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]

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.

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

@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

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

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.

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

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

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

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

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

$ 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!

@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

[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

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

[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

@sToRmInG - Thanks!

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

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

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.

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

Danke! - Thank you

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.

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.

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.

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!

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

@ajgraves, thanks a lot!

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

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

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

java-openjfx should be added to the dependent packages.

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

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.

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

-s, --syncdeps   Install missing dependencies with pacman

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

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

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

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

How are you building the package?

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

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

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

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

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.

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

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.

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.

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

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

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

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

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.

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

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

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?

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

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.

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 \

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

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

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.

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

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

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

To: binaryanomaly

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

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.

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

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

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?

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