Skip to content
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

Closed
vanniktech opened this issue Dec 29, 2018 · 12 comments
Closed

Unable to unlock vault on Ubuntu 18.04 #788

vanniktech opened this issue Dec 29, 2018 · 12 comments

Comments

@vanniktech
Copy link

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:

11:54:56.172 [JavaFX Application Thread] ERROR o.c.u.controllers.UnlockedController - Reveal failed.
org.cryptomator.ui.model.Volume$VolumeException: org.cryptomator.frontend.fuse.mount.ProcessUtil$CommandTimeoutException: Command timed out.
  at org.cryptomator.ui.model.FuseVolume.reveal(FuseVolume.java:95)
  at org.cryptomator.ui.model.Vault.reveal(Vault.java:161)
  at org.cryptomator.ui.controllers.UnlockedController.lambda$revealVault$7(UnlockedController.java:175)
  at org.cryptomator.ui.util.Tasks.lambda$create$0(Tasks.java:33)
  at org.cryptomator.ui.util.Tasks$TaskImpl.call(Tasks.java:139)
  at javafx.graphics/javafx.concurrent.Task$TaskCallable.call(Unknown Source)
  at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
  at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
  at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
  at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
  at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
  at java.base/java.lang.Thread.run(Unknown Source)
Caused by: org.cryptomator.frontend.fuse.mount.ProcessUtil$CommandTimeoutException: Command timed out.
  at org.cryptomator.frontend.fuse.mount.ProcessUtil.waitFor(ProcessUtil.java:66)
  at org.cryptomator.frontend.fuse.mount.ProcessUtil.startAndWaitFor(ProcessUtil.java:46)
  at org.cryptomator.frontend.fuse.mount.LinuxMounter$LinuxMount.revealInFileManager(LinuxMounter.java:59)
  at org.cryptomator.ui.model.FuseVolume.reveal(FuseVolume.java:92)
  ... 11 common frames omitted
11:55:09.483 [Thread-21] ERROR o.c.frontend.fuse.ReadOnlyAdapter - getattr failed.
java.nio.file.ClosedFileSystemException: null
  at org.cryptomator.cryptofs.CryptoFileSystemImpl.assertOpen(CryptoFileSystemImpl.java:509)
  at org.cryptomator.cryptofs.CryptoPath.<init>(CryptoPath.java:38)
  at org.cryptomator.cryptofs.CryptoPath.copyWithElements(CryptoPath.java:344)
  at org.cryptomator.cryptofs.CryptoPath.resolve(CryptoPath.java:189)
  at org.cryptomator.cryptofs.CryptoPath.resolve(CryptoPath.java:196)
  at org.cryptomator.cryptofs.CryptoDirectoryStream.decrypt(CryptoDirectoryStream.java:124)
  at java.base/java.util.stream.ReferencePipeline$3$1.accept(Unknown Source)
  at java.base/java.util.stream.ReferencePipeline$2$1.accept(Unknown Source)
  at java.base/java.util.stream.ReferencePipeline$3$1.accept(Unknown Source)
  at java.base/java.util.stream.ReferencePipeline$2$1.accept(Unknown Source)
  at java.base/java.util.stream.ReferencePipeline$3$1.accept(Unknown Source)
  at java.base/java.util.stream.ReferencePipeline$3$1.accept(Unknown Source)
  at java.base/java.util.Spliterators$IteratorSpliterator.tryAdvance(Unknown Source)
  at java.base/java.util.stream.StreamSpliterators$WrappingSpliterator.lambda$initPartialTraversalState$0(Unknown Source)
  at java.base/java.util.stream.StreamSpliterators$AbstractWrappingSpliterator.fillBuffer(Unknown Source)
  at java.base/java.util.stream.StreamSpliterators$AbstractWrappingSpliterator.doAdvance(Unknown Source)
  at java.base/java.util.stream.StreamSpliterators$WrappingSpliterator.tryAdvance(Unknown Source)
  at java.base/java.util.Spliterators$1Adapter.hasNext(Unknown Source)
  at com.google.common.collect.Iterators.size(Iterators.java:163)
  at com.google.common.collect.Iterables.size(Iterables.java:126)
  at org.cryptomator.frontend.fuse.ReadOnlyDirectoryHandler.countSubDirs(ReadOnlyDirectoryHandler.java:48)
  at org.cryptomator.frontend.fuse.ReadOnlyDirectoryHandler.getattr(ReadOnlyDirectoryHandler.java:38)
  at org.cryptomator.frontend.fuse.ReadWriteDirectoryHandler.getattr(ReadWriteDirectoryHandler.java:19)
  at org.cryptomator.frontend.fuse.ReadOnlyAdapter.getattr(ReadOnlyAdapter.java:127)
  at ru.serce.jnrfuse.AbstractFuseFS.lambda$init$1(AbstractFuseFS.java:96)
  at jnr.ffi.provider.jffi.NativeClosureProxy$$impl$$0.invoke(Unknown Source)

Using WebDAV works on my system so I'm not blocked. Thanks for this awesome tool!

@cooocky

This comment has been minimized.

@overheadhunter
Copy link
Member

@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.

@infeo
Copy link
Member

infeo commented Jan 30, 2019

@vanniktech Does the log file show any error before the "Reveal failed" message?

@vanniktech
Copy link
Author

Nope.

@overheadhunter
Copy link
Member

Might be related to #804?

@Handwrit
Copy link

Handwrit commented Apr 3, 2019

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.

@stale
Copy link

stale bot commented Jun 14, 2019

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.

@stale stale bot added the state:stale Issues without any activity that will be closed automatically label Jun 14, 2019
@vanniktech
Copy link
Author

It's still an issue.

@stale stale bot removed the state:stale Issues without any activity that will be closed automatically label Jun 15, 2019
@stale
Copy link

stale bot commented Sep 13, 2019

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.

@stale stale bot added the state:stale Issues without any activity that will be closed automatically label Sep 13, 2019
@vanniktech
Copy link
Author

I'm on a new machine where I don't have this problem.

@stale stale bot removed the state:stale Issues without any activity that will be closed automatically label Sep 13, 2019
@stale
Copy link

stale bot commented Dec 12, 2019

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.

@stale stale bot added the state:stale Issues without any activity that will be closed automatically label Dec 12, 2019
@vanniktech
Copy link
Author

No longer interested in this. Feel free to close.

@stale stale bot removed the state:stale Issues without any activity that will be closed automatically label Dec 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants