I
Ubuntu 18.04
Cryptomator 1.4.6
Expected was that step 4 mounts the vault.
16:24:20.260 [Background Thread 6] DEBUG o.cryptomator.cryptofs.ReadonlyFlag - Vault opened for read and write.I have the same thing
Some additionals:
This issues does not happen with version 1.4.2
+1
I can confirm this bug.
The only way right now to successfully unlock a vault after entering a wrong password is to actually kill the application and restart which becomes tedious if you have fat fingers at times :/
Most helpful comment
I have the same thing
Some additionals:
This issues does not happen with version 1.4.2