etelia
June 11, 2023, 4:04pm
1
Hi, does anybody use Cryptomator on NixOS with FUSE?
How can I get it running?
Cheers
I also have problems on NixOS.
FUSE itself works, other applications that use FUSE also seem to work (for example rclone).
Apparently Cryptomator doesn’t really get how FUSE is working on NixOS. Maybe it is looking in the wrong places or something. I dunno. Maybe I’ll ask the nixpkgs
package maintainer of this package…
I found this
opened 12:21PM - 23 Sep 23 UTC
closed 09:14PM - 13 Nov 23 UTC
0.kind: bug
### Describe the bug
In the vault options, vaults can only be mounted as `WebDA… V (HTTP Address)`.
### Steps To Reproduce
Steps to reproduce the behavior:
1. Launch cryptomator
2. Go to a vault options
3. In the `Virtual Drive` tab, the `Volume Type` combo box does not contain a FUSE item
### Expected 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:
```
14:19:36.332 [main] INFO org.cryptomator.common.Environment - java.library.path: /nix/store/gplxx8rm08abic60i4iib99pcabbdgq1-fuse-3.11.0/lib:/usr/java/packages/lib:/usr/lib64:/lib64:/lib:/usr/lib
```
Full console output:
```
14:19:36.290 [main] INFO o.c.common.settings.SettingsProvider - Settings loaded from /home/nicomem/.config/Cryptomator/settings.json
14:19:36.332 [main] INFO org.cryptomator.common.Environment - user.home: /home/nicomem
14:19:36.332 [main] INFO org.cryptomator.common.Environment - java.library.path: /nix/store/gplxx8rm08abic60i4iib99pcabbdgq1-fuse-3.11.0/lib:/usr/java/packages/lib:/usr/lib64:/lib64:/lib:/usr/lib
14:19:36.332 [main] INFO org.cryptomator.common.Environment - user.language: en
14:19:36.332 [main] INFO org.cryptomator.common.Environment - user.region: null
14:19:36.332 [main] INFO org.cryptomator.common.Environment - logback.configurationFile: null
14:19:36.332 [main] INFO org.cryptomator.common.Environment - cryptomator.settingsPath: ~/.config/Cryptomator/settings.json
14:19:36.332 [main] INFO org.cryptomator.common.Environment - cryptomator.ipcSocketPath: ~/.config/Cryptomator/ipc.socket
14:19:36.332 [main] INFO org.cryptomator.common.Environment - cryptomator.integrationsWin.keychainPaths: null
14:19:36.332 [main] INFO org.cryptomator.common.Environment - cryptomator.logDir: ~/.local/share/Cryptomator/logs
14:19:36.332 [main] INFO org.cryptomator.common.Environment - cryptomator.loopbackAlias: null
14:19:36.332 [main] INFO org.cryptomator.common.Environment - cryptomator.pluginDir: ~/.local/share/Cryptomator/plugins
14:19:36.332 [main] INFO org.cryptomator.common.Environment - cryptomator.mountPointsDir: ~/.local/share/Cryptomator/mnt
14:19:36.332 [main] INFO org.cryptomator.common.Environment - cryptomator.minPwLength: null
14:19:36.332 [main] INFO org.cryptomator.common.Environment - cryptomator.appVersion: 1.9.4
14:19:36.332 [main] INFO org.cryptomator.common.Environment - cryptomator.buildNumber: nix
14:19:36.332 [main] INFO org.cryptomator.common.Environment - cryptomator.showTrayIcon: false
14:19:36.332 [main] INFO org.cryptomator.common.Environment - cryptomator.p12Path: null
14:19:36.332 [main] INFO o.cryptomator.launcher.Cryptomator - Starting Cryptomator 1.9.4 on Linux 6.5.4 (amd64)
14:19:36.342 [main] INFO org.cryptomator.ipc.Server - Spawning IPC server listening on socket /home/nicomem/.config/Cryptomator/ipc.socket
14:19:36.483 [JavaFX Application Thread] INFO o.cryptomator.launcher.Cryptomator - JavaFX runtime started after 302ms
```
### Notify maintainers
@bachp
### Metadata
```console
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
- system: `"x86_64-linux"`
- host os: `Linux 6.5.4, NixOS, 23.11 (Tapir), 23.11.20230919.5ba549e`
- multi-user?: `yes`
- sandbox: `yes`
- version: `nix-env (Nix) 2.17.0`
- channels(root): `"nixos"`
- channels(nicomem): `""`
- nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`
```
And someone who self-assigned the issue to themself said:
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.
So yeah something is weird, but at least I see some recent activity.
infeo
November 16, 2023, 11:02am
4
This problem is fixed with latest Cryptomator 1.11.0 release