-
Notifications
You must be signed in to change notification settings - Fork 5
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
Error: E5BN:E5BN:BIEF and Error: 296J:8B6S:HUCA #14
Comments
The issue has been resolved after installing fuse2: |
Thank you for reporting the bug. With what you found out I was able to reproduce it. If fuse2 is not on the system, Cryptomator cannot mount the vault. On Ubuntu I wasn't able to reproduce it, because Flatpak installs Fuse2 as a dependency. Arch, on the other hand, installs Fuse3, Cryptomator currently requires Fuse2 so the problem occurs on Arch, but not on Ubuntu. We need to check why this declared fuse dependy in Flatpak doesn't work: org.cryptomator.Cryptomator/org.cryptomator.Cryptomator.yaml Lines 26 to 37 in 1ec15d8
|
Got it, in line 31 we overwrite the
Tried to remove the The problem now is that Cryptomator does not check if Fuse is installed at all and if so in which version which is quite irritating especially with a packet format which is supposed to do exactly that, encapsulate runtime dependencies. Will create an issue in the Cryptomator repo to address this. The workaround is and remains exactly your described, install Fuse2 (later Fuse3), but a user should know in any case what to do. Edit: Here it is: cryptomator/cryptomator#2539 |
OS: Linux / 6.0.5-arch1-1
App: 1.6.15 / flatpak-1
Neofetch:
This error shows up when attempting to unlock a vault. I tried both FUSE and WebDAV, but neither of them worked.
FUSE:
WebDAV:
The text was updated successfully, but these errors were encountered: