locking of vault fails, probable reason is typo in path

[the-wolfman]

Issue:

Locking of vault fails on Cryptomator: 1.6.12 installed from flat hub and running on flatpak 1.6.5-0ubuntu0.4
Error message is " ... was blocked by pending operations or open files ...".
Force lock does produce the same result. Can not quit cryptomator.

Log shows

"Caused by: org.cryptomator.frontend.fuse.mount.FuseMountException: Unmount failed. STDERR: fusermount: failed to unmount /home/xxx/.local/share/cryptomator/mnt/test1: device or resource busy"

Likely cause:

The expected local mount path passed to fusermount is "/home/xxx/local/share/cryptomator". However, in the ubuntu filesystem the existing path is "/home/xxx/.local/share/Cryptomator".
This path is case sensitive, hence the values will not match. Reason may be a typo introducing a capital "C" into the path.

[cwmke]

Issue also appears in Fedora 36 & 37.

[SailReal]

On my Ubuntu virtual machine it works as expected using Flatpak. Haven't verified it in code but when I lock the vault with an open process handle, I see the lower case path too. If I close the process handle, the vault is closed as expected. So my guess is that the lower case path is just a "display thing".

So the question is what is still accessing the mount point. You can check that with lsof PATH_TO_MOUNT_POINT, so in your case lsof /home/xxx/.local/share/Cryptomator/mnt/test1

Does it show a program?

[cwmke]

That ended up being the case for me. The thumbnailer was hanging on certain files for some reason.

[SailReal]

Thank you for confirming.

[jahed]

I ran lsof PATH_TO_MOUNT_POINT and saw xdg-document-portal was holding onto some files. This is a known issue: flatpak/xdg-desktop-portal#689.

systemctl --user restart xdg-document-portal cleared that up and let me lock the vault.