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.
Search Criteria
Package Details: cryptomator 1.12.3-1
Package Actions
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: | 79 |
Popularity: | 0.56 |
First Submitted: | 2016-04-03 17:36 (UTC) |
Last Updated: | 2024-02-27 15:44 (UTC) |
Dependencies (10)
- alsa-lib
- fuse3 (fuse3-gitAUR)
- hicolor-icon-theme (hicolor-icon-theme-gitAUR)
- libnet (libnet-gitAUR)
- libxrender
- libxtst
- maven (mvnvmAUR) (make)
- unzip (unzip-natspecAUR, unzip-zstdAUR) (make)
- keepassxc-cryptomatorAUR (optional) – Use KeePassXC to store vault passwords
- ttf-hanazono (optional) – Install this font when using Japanese system language
Required by (1)
Sources (2)
Latest Comments
« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 12 13 .. 17 Next › Last »
ajgraves commented on 2021-07-09 21:10 (UTC)
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:
- Install
zulu-16-bin
oramazon-corretto-16
sudo archlinux-java set zulu-16
oramazon-corretto-16
PATH=/usr/lib/jvm/default/bin:$PATH
- 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
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.