cryptomator icon indicating copy to clipboard operation
cryptomator copied to clipboard

Locking vault results in cryptomator hanging

Open simphide opened this issue 1 year ago • 4 comments

Please agree to the following

Summary

When I try to lock my vault the locking process fails and the webdav mount is still displayed (while not beeing accessible). The only solution is to restart my Mac

What software is involved?

  • Operating System: macOS Sonoma (14.5)
  • Cryptomator: 1.12.3
  • Nextcloud 3.13.0
  • Processor: Mac Silicon M3 Pro

Volume Type

WebDAV (AppleScript)

Steps to Reproduce

  1. Unlock vault
  2. work with vault (e.g. add file)
  3. Lock vault

Expected Behavior

Vault gets successfully locked

Actual Behavior

Locking fails, force lock fails aswell and webdav is still shown while not being accessible image

Reproducibility

Always

Relevant Log Output

16:49:58.919 [JavaFX Application Thread] DEBUG o.c.common.vaults.VaultStats - stop recording stats
16:49:58.926 [JavaFX Application Thread] DEBUG o.c.ui.fxapp.FxApplicationWindows - Start lock workflow for XXX
16:50:08.942 [App Background Thread 006] INFO  o.cryptomator.ui.lock.LockWorkflow - Locking XXX - XXX (forced: false).
org.cryptomator.integrations.mount.UnmountFailedException: java.util.concurrent.TimeoutException
	at [email protected]/org.cryptomator.frontend.webdav.mount.MacAppleScriptMounter$MountImpl.unmount(MacAppleScriptMounter.java:154)
	at [email protected]/org.cryptomator.frontend.webdav.mount.MacAppleScriptMounter$MountImpl.unmount(MacAppleScriptMounter.java:136)
	at [email protected]/org.cryptomator.common.vaults.Vault.lock(Vault.java:174)
	at [email protected]/org.cryptomator.ui.lock.LockWorkflow.lock(LockWorkflow.java:63)
	at [email protected]/org.cryptomator.ui.lock.LockWorkflow.call(LockWorkflow.java:57)
	at [email protected]/org.cryptomator.ui.lock.LockWorkflow.call(LockWorkflow.java:34)
	at [email protected]/javafx.concurrent.Task$TaskCallable.call(Unknown Source)
	at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
	at java.base/java.util.concurrent.CompletableFuture$AsyncRun.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: java.util.concurrent.TimeoutException: null
	at [email protected]/org.cryptomator.frontend.webdav.mount.ProcessUtil.waitFor(ProcessUtil.java:59)
	at [email protected]/org.cryptomator.frontend.webdav.mount.ProcessUtil.startAndWaitFor(ProcessUtil.java:42)
	at [email protected]/org.cryptomator.frontend.webdav.mount.MacAppleScriptMounter$MountImpl.unmount(MacAppleScriptMounter.java:151)
	... 11 common frames omitted
16:50:08.972 [JavaFX Application Thread] DEBUG o.c.ui.fxapp.FxApplicationWindows - visible windows: 2
16:50:09.651 [webdav-027] DEBUG o.c.w.core.filters.LoggingFilter - REQUEST 253:
LOCK /C8FczEFSGNzo/XXX/2024/2024-06-03%20XXX%20XXX%XXX%20XXX%20XXX.pdf HTTP/1.1
Accept: */*
Timeout: Second-600
User-Agent: WebDAVFS/3.0.0 (03008000) Darwin/23.5.0 (arm64)
Connection: keep-alive
Host: localhost:42427
Content-Length: 229
Depth: 0
Content-Type: text/xml; charset="utf-8"

Anything else?

No response

simphide avatar Jun 04 '24 14:06 simphide

I think this is the same issue like https://github.com/cryptomator/cryptomator/issues/3326

simphide avatar Jun 04 '24 19:06 simphide

So I couldn't reproduce the error with the steps you mentioned @simphide (bolded items are where we differ):

  1. unlock vault
  2. add file to vault
  3. lock vault

The software I used was

  • Operating System: macOS Sonoma (14.2.1)
  • Cryptomator: 1.12.3
  • Processor: Mac Silicon M3 Max

Regarding logs: there wasn't an UnmountFailedException

Dollabilliam avatar Jun 12 '24 04:06 Dollabilliam

I also encountered this problem when I opened the pictures in the vault

CapZhang avatar Jun 22 '24 02:06 CapZhang

I have faced the same issue, even while browsing photos/pictures in the vault.

EDIT: I tried just adding files without opening them and the vault did close properly. Now, when I opened the vault again, opened the picture and then tried closing the vault. I see it getting stuck.

brosahay avatar Aug 30 '24 21:08 brosahay