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.

@gregsie Then, please open an issue here: https://github.com/cryptomator/cryptomator/issues/new/choose.

Please provide info about the desktop environment, window manager and scaling factor you use. And a screenshot might help. Thanks.

@puejava thanks for the info. Yes, setting GDK_SCALE=2 makes a big difference, maybe too big but everything is readable :) I don't think that setting allows fractional increments

@gregsie Set the environment variable GDK_SCALE=2 and see if this works for you.

Thanks to all for the package, it works really well

i just have a single issue the font is tiny and difficult to read. ( I have a HDPI monitor) I've tried exporting _JAVA_OPTIONS and I can see the application picks them up at runtime but nothing changes in the interface. Does anyone have any recommendations?

This works perfectly for my other java applications such as diylc -Dswing.aatext=true -Dswing.plaf.metal.controlFont=lucon-plain-18 Dswing.plaf.metal.userFont=lucon-plain-20

Recently I had the problem that I couldn't install upgrade for this package.

==> Validating source_x86_64 files with sha256sums...
    jdk.tar.gz ... FAILED
    openjfx.zip ... FAILED
==> ERROR: One or more files did not pass the validity check!

After cleaning the AUR cache (eg. paru -Scca) updated dependencies passed the validity check.

Update: I'm stupid, the answer is in the error.

Now, I have to figure out what install made that change and whether anything else will be messed up without that string.

Since the 16th, my Cryptomator install stopped working. I tried updating, would get the same error. Tried fresh installing cryptomator, javafx, and openjdk but get the same error. Since I am able to install the same versions of javafx and openjdk without error, I tried stripping the included javafx/jdk out of the pkgbuild to build against the system, same error.

I then tried to install via maven, that failed all the same. Always with the same error. Even the appimage build (cryptomator-bin) has the same problem.

Tried installing previous versions (eg: v1.11.1, v1.10.0) and still have the same problem.

So, to me, it appears to be related to the updated javafx and/or openjdk against cryptomator updates that don't appear to be compatible.

jdk-21.0.2+13/NOTICE
Archive:  openjfx.zip
  inflating: jmods/javafx.graphics.jmod  
  inflating: jmods/javafx.controls.jmod  
  inflating: jmods/javafx.fxml.jmod  
  inflating: jmods/javafx.base.jmod  
Picked up _JAVA_OPTIONS: ’-Dswing.aatext=TRUE -Dawt.useSystemAAFontSettings=on’
Unrecognized option: ’-Dswing.aatext=TRUE
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: cryptomator-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
cryptomator - exit status 4

I do not remember the last working version I had, but I do keep things up to date.

None of this makes any sense as it was working fine last week.

Anyone else have this issue? Anyone find a way around it?

We need to skip 1.12.0 because of https://github.com/cryptomator/cryptomator/issues/3315 and will update tomorrow directly to 1.12.1

Thanks @xiota, applied your suggestions and will be available within the next update of pkgrel or pkgver.

@PortableAlgebra As you may have noticed, we have finally updated Cryptomator to the latest version on 2023-11-08. In the future, the problem can no longer arise as the JDK and JavaFX against which we want to build is now downloaded as a source.