Hi Community,
I have recently paid for the iOS version and find the UI underwhelming. I have an encrypted vault stored on Google Drive. I want to edit files on Linux, I am using Solus. However, when I open vault on Linux, there are no files. If I create a directory on Linux, I can see it and if I add a file to the directory then the directory disappears from the Linux mount when I reload.
I’ve checked the logs and there are no exceptions.
I am also experiencing the same issue on Linux. I have a machine using Cryptomator on Windows through Google Drive. When I access that vault on Linux using FUSE or WebDAV neither will show me the files after unlock. I am using 1.5.11 and the vault was established using that same version on Windows platform. Also, the reveal drive button does not work.
WebDAV log when trying to reveal:
09:57:34.431 [webdav-039] DEBUG o.c.w.core.filters.LoggingFilter - RESPONSE 6:
207
Content-Encoding: gzip
Accept-Encoding: deflate, gzip
Date: Sat, 02 Jan 2021 14:57:32 GMT
Content-Type: text/xml;charset=utf-8
09:57:34.437 [JavaFX Application Thread] INFO o.cryptomator.ui.common.VaultService - Revealed 1pC9gvS7dU-UuBKy2V6Pdpjy_oZiKtBYV
09:57:35.366 [webdav-039] DEBUG o.c.w.core.filters.LoggingFilter - REQUEST 7:
PROPFIND /D7CMeGBkNEfT/1pC9gvS7dU_UuBKy2V6Pdpjy_oZiKtBYV/ HTTP/1.1
Apply-To-Redirect-Ref: T
Connection: keep-alive
User-Agent: gvfs/1.46.1
Host: localhost:42427
Accept-Encoding: gzip, deflate
Accept-Language: en-us, en;q=0.9
Content-Length: 235
Depth: 0
Content-Type: application/xml
09:57:35.373 [webdav-039] DEBUG o.c.w.core.filters.LoggingFilter - RESPONSE 7:
207
Content-Encoding: gzip
Accept-Encoding: deflate, gzip
Date: Sat, 02 Jan 2021 14:57:35 GMT
Content-Type: text/xml;charset=utf-8
Logs trying to reveal using FUSE
09:59:34.155 [JavaFX Application Thread] INFO o.cryptomator.ui.common.VaultService - Revealed 1pC9gvS7dU-UuBKy2V6Pdpjy_oZiKtBYV
09:59:35.625 [Thread-629] TRACE o.c.f.fuse.locks.PathRLockImpl - Acquired read path lock for '[]'
09:59:35.626 [Thread-629] TRACE o.c.f.fuse.locks.DataRLockImpl - Acquired read data lock for '[]'
09:59:35.638 [Thread-629] TRACE o.c.frontend.fuse.ReadOnlyAdapter - getattr / (lastModifiedTime: 2020-12-28T19:29:41Z, lastAccessTime: 1969-12-31T23:59:59Z, creationTime: 2020-12-28T19:29:41Z, isRegularFile: false, isDirectory: true, isSymbolicLink: false, isOther: false, size: 0, fileKey: (dev=34,ino=10))
09:59:35.638 [Thread-629] TRACE o.c.f.fuse.locks.DataRLockImpl - Released read data lock for '[]'
09:59:35.638 [Thread-629] TRACE o.c.f.fuse.locks.PathRLockImpl - Released read path lock for '[]'
I managed to find an alternate solution. Its a little manual but its sufficient for my workflow.
I believe the problem is related to latency in the Gnome Google driver that mounts the Drive. I used the drive CLI tool to mount my drive on a folder, create the encrypted folder and then push and pull when I want to update the encrypted contents.