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.
Search Criteria
Package Details: cryptomator 1.14.2-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, as.skymatic) |
| Last Packager: | as.skymatic |
| Votes: | 81 |
| Popularity: | 0.45 |
| First Submitted: | 2016-04-03 17:36 (UTC) |
| Last Updated: | 2024-11-19 11:41 (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)
tobihagemann commented on 2019-01-20 09:32 (UTC) (edited on 2019-01-20 09:33 (UTC) by tobihagemann)
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.
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.