You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using Linux in version: Manjaro
DE: KDE Plasma 5.11.3
Kernel: 4.14
I'm running Cryptomator in version: 1.3.1
Description
I created a Cryptomator vault and tryed to work with / in it. But there are some problems, so that it is nearly unusable.
with dav:
Situation 1:
I simply want to copy a file into the vault using my default file manager, dolphin. It fails with this error message:
It means "Failed to write file. Not enough space."
At the bottom right, dolphin displays the free space. In the case of the Cryptomator vault, it says:
Translated: "Unknown size"
My current solution: I have to open a Terminal in the vault and use the cp command to copy file into the vault.
But that should not be a real 'solution'.
Situation 2:
Some applications don't support saving to the dav / webdav mountpoint. For example LibreOffice when I try to save a file with LibreOffice:
I can't even open a file from within the vault with LibreOffice:
My current solution: Copy the file outside of the vault, edit it there, and copy it back using the cp command.
Problem 1: not userfriendly
Problem 2: when the file is outside of the vault, it is unencrypted during editing
so I tryed webdav:
Back to Situation 1:
Copying files using dolphin now works. (Yey :D)
But I can't open the vault from within Cryptomator anymore. I have to copy the url and paste it in dolphin.
Back to Situation 2:
The problems with other apps still exist. Again, LibreOffice example, trying to save to the vault:
I guess it has something to do with the current mount system. Would it be possible, to mount the vault in a 'real' local folder? For example in "/home/myuser/CryptomatorVault/"? This is like for example cryfs is doing it and it works perfectly.
Maybe you ask now: Why aren't you using CryFS?
The problem with CryFS is: It creates too much small files. That takes much more time to sync with Dropbox, so I wanted to try out Cryptomator.
The text was updated successfully, but these errors were encountered:
Basic Info
I'm using Linux in version: Manjaro
DE: KDE Plasma 5.11.3
Kernel: 4.14
I'm running Cryptomator in version: 1.3.1
Description
I created a Cryptomator vault and tryed to work with / in it. But there are some problems, so that it is nearly unusable.
with dav:
Situation 1:
I simply want to copy a file into the vault using my default file manager, dolphin. It fails with this error message:
It means "Failed to write file. Not enough space."
At the bottom right, dolphin displays the free space. In the case of the Cryptomator vault, it says:
Translated: "Unknown size"
My current solution: I have to open a Terminal in the vault and use the cp command to copy file into the vault.
But that should not be a real 'solution'.
Situation 2:
Some applications don't support saving to the dav / webdav mountpoint. For example LibreOffice when I try to save a file with LibreOffice:
I can't even open a file from within the vault with LibreOffice:
My current solution: Copy the file outside of the vault, edit it there, and copy it back using the cp command.
Problem 1: not userfriendly
Problem 2: when the file is outside of the vault, it is unencrypted during editing
so I tryed webdav:
Back to Situation 1:
Copying files using dolphin now works. (Yey :D)
But I can't open the vault from within Cryptomator anymore. I have to copy the url and paste it in dolphin.
Back to Situation 2:
The problems with other apps still exist. Again, LibreOffice example, trying to save to the vault:
I guess it has something to do with the current mount system. Would it be possible, to mount the vault in a 'real' local folder? For example in "/home/myuser/CryptomatorVault/"? This is like for example cryfs is doing it and it works perfectly.
Maybe you ask now: Why aren't you using CryFS?
The problem with CryFS is: It creates too much small files. That takes much more time to sync with Dropbox, so I wanted to try out Cryptomator.
The text was updated successfully, but these errors were encountered: