-
-
Notifications
You must be signed in to change notification settings - Fork 981
-
-
Notifications
You must be signed in to change notification settings - Fork 981
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
Unable to unlock vault on Ubuntu 18.04 #788
Comments
This comment has been minimized.
This comment has been minimized.
@cooocky your issue is a duplicate of #752, where you will find a workaround. It is not related to the stack trace posted by @vanniktech. |
@vanniktech Does the log file show any error before the "Reveal failed" message? |
Nope. |
Might be related to #804? |
I'm on 18.04 as well, and I'm getting the same error, with release 1.4.6. I don't think it's accurate to consider Cryptomator a Linux application. It may work on some exotic distros, but not the most common one. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
It's still an issue. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I'm on a new machine where I don't have this problem. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
No longer interested in this. Feel free to close. |
I'm using Ubuntu 18.04 with Cryptomator 1.4.0 which I installed via
apt-get
. My files are all in Google Drive which I sync via google-drive-ocamlfuse.When using FUSE and trying to unlock my vault I'm getting the following exception:
Using WebDAV works on my system so I'm not blocked. Thanks for this awesome tool!
The text was updated successfully, but these errors were encountered: