Package Details: cryptomator-bin 1.16.0-1

Git Clone URL: https://aur.archlinux.org/cryptomator-bin.git (read-only, click to copy)
Package Base: cryptomator-bin
Description: Multiplatform transparent client-side encryption of your files in the cloud.
Upstream URL: https://cryptomator.org/
Keywords: AppImage binary cryptography encryption
Licenses: GPL3
Conflicts: cryptomator
Provides: cryptomator
Replaces: cryptomator
Submitter: ajgraves
Maintainer: ajgraves (overheadhunter, SailReal, as.skymatic)
Last Packager: SailReal
Votes: 32
Popularity: 0.23
First Submitted: 2021-05-02 19:50 (UTC)
Last Updated: 2025-04-29 11:24 (UTC)

Pinned Comments

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

Hello everyone! This is a new package, created from cryptomator which is being updated to build from source. This package will always install the latest binary (AppImage) as built from upstream. If you'd rather build the app from source, please use the cryptomator package instead.

Latest Comments

1 2 3 Next › Last »

SailReal commented on 2025-05-06 12:07 (UTC)

Oh, @KingElrond, you are right, will have a look at it!

KingElrond commented on 2025-05-06 11:45 (UTC) (edited on 2025-05-07 15:24 (UTC) by KingElrond)

Hi!

I think there is a problem with this package. The icon in the tray area of kde/plasma 6 stays white even on light themes, making it almost invisible. On the contrary, the appimage from cryptomator websites is well behaved, as the icon changes to black/white according to light/white theme.

I think that the problem lies in the icons bundled separately to the appimage in the AUR package.

org.cryptomator.Cryptomator.svg
org.cryptomator.Cryptomator.tray.svg
org.cryptomator.Cryptomator.tray-unlocked.svg

and possibly org.cryptomator.Cryptomator.png(maybe this one is just for the menu item?)

From a quick test, when these icons are removed from the PKGBUILD and the .SRCINFO the program behaves correctly (i.e., the tray icon changes according to the used theme (light/dark)).

Could you please look into it?

Github issue, for reference: https://github.com/cryptomator/cryptomator/issues/3775#issuecomment-2844213638

Thanks a lot in advance!

j.mlr commented on 2025-04-01 09:39 (UTC)

@RunasSudo thanks for posting this. For the time being, I just downgrade fuse3 to 3.16.2, this is probably not a good solution but hey I need my files to be decrypted.

RunasSudo commented on 2025-04-01 09:25 (UTC)

FYI there's an upstream issue in the current version of Cryptomator (1.15.1) that is incompatible with fuse3 3.17.1. See discussion and workaround at https://github.com/cryptomator/cryptomator/discussions/3793#discussioncomment-12686261

Brian76348693458 commented on 2025-02-04 20:28 (UTC)

Thanks, SailReal! :)

SailReal commented on 2025-02-04 20:20 (UTC)

@Brian76348693458 see https://github.com/cryptomator/cryptomator/issues/3717 regarding this topic.

Brian76348693458 commented on 2025-02-04 20:19 (UTC)

Hey! After building 1.15.0-1, Cryptomator does not start anymore.

"execv error: No such file or directory"

Can you fix the package or can I do something to make it work?

/usr/bin/cryptomator links to /opt/cryptomator-bin/cryptomator-1.15.0-x86_64.AppImage which exists at the given location.

hwmpunk commented on 2024-09-24 05:08 (UTC)

There's a new version 1.14 if somebody can please update it? Thank you!

SailReal commented on 2023-06-04 19:06 (UTC)

@mewsen thanks for the hint. AppImages still require Fuse2 to run. Added fuse2 as dependency.

1 2 3 Next › Last »