-
-
Notifications
You must be signed in to change notification settings - Fork 14.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cryptomator: Cannot mount vault as FUSE volume #256886
Comments
I think this might be related to cryptomator/fuse-nio-adapter#72 It seems since they switched to the new fuse integration they only search a predefined number of paths. This is also consistent as the nix build of cryptomator works on non nixos linux. |
I have the same issue. Does somebody have some workaraound yet? EDIT: so what I am currently doing, which is really not ideal, is just mounting the webdav directory with rclone, which, well, uses FUSE. so yeah rclone has no problems with using FUSE... |
The fix for this is merged but not yet released cryptomator/fuse-nio-adapter#81. It's in the 4.0.0 milestone of fuse-nio-adapter. I'm currently using the flapak version of Cryptomator. |
thank you for the answer! i don't quite understand what I'm gonna try the flatpak version of Cryptomator out, thanks for the hint. I actually tried out appimage, but that didn't change anything. |
In the 1.11.0-beta2 release of cryptomator, vaults are able to be mounted as FUSE volumes. So once 1.11.0 is fully released (and the nixpkgs version updated), this issue should be fixed. Until the new version of cryptomator is released, you could create an overlay to use the beta version, like I am doing at the moment. let
jdk = jdk21.override {
enableJavaFX = true;
};
... |
thank you for your response! i hope i am not rude to ask for your help in achieving this myself. i put the following in my overlays = [
(final: prev: {
cryptomator = prev.cryptomator.overrideAttrs (old: {
src = prev.fetchFromGitHub {
owner = "cryptomator";
repo = "cryptomator";
rev = "1.11.0-beta2";
hash = "sha256-QYVvu1BrOGoz+gOGXGt3Y08H8ufnHhQDDp1H/MsDC/k=";
};
});
})
]; and i also did the i get the following error when building:
haven't been able to successfully find a solution via search engines... |
For overlays, I simply copy the nix files and doing the following overlay: final: prev:
let
inherit (final) callPackage;
in
{
cryptomator = callPackage ./cryptomator {};
} This is quite crude, and there is probably a better way to do it, but it at least avoids any weird errors like the one you are having. |
Describe the bug
In the vault options, vaults can only be mounted as
WebDAV (HTTP Address)
.Steps To Reproduce
Steps to reproduce the behavior:
Virtual Drive
tab, theVolume Type
combo box does not contain a FUSE itemExpected behavior
Vaults can be mounted as FUSE volumes
Additional context
In the console output, cryptomator seems to have access to the fuse3 libs in its PATH:
Full console output:
Notify maintainers
@bachp
Metadata
The text was updated successfully, but these errors were encountered: