I keep getting this error trying to unlock my vaults from the Linux Appimage Client

… and it doesn’t matter what password i use, even with random text i still get the same error. The vaults unlock fine on windows (this is Ubuntu 21.04 btw)

java.nio.file.AccessDeniedException: /path/to/vault/c

	at java.base/sun.nio.fs.UnixException.translateToIOException(Unknown Source)

	at java.base/sun.nio.fs.UnixException.rethrowAsIOException(Unknown Source)

	at java.base/sun.nio.fs.UnixException.rethrowAsIOException(Unknown Source)

	at java.base/sun.nio.fs.UnixFileSystemProvider.createDirectory(Unknown Source)

	at java.base/java.nio.file.Files.createDirectory(Unknown Source)

	at java.base/java.nio.file.Files.createAndCheckIsDirectory(Unknown Source)

	at java.base/java.nio.file.Files.createDirectories(Unknown Source)

	at org.cryptomator.cryptofs.common.FileSystemCapabilityChecker.determineSupportedFileNameLength(FileSystemCapabilityChecker.java:118)

	at org.cryptomator.cryptofs.common.FileSystemCapabilityChecker.determineSupportedFileNameLength(FileSystemCapabilityChecker.java:95)

	at org.cryptomator.common.vaults.Vault.createCryptoFileSystem(Vault.java:115)

	at org.cryptomator.common.vaults.Vault.unlock(Vault.java:147)

	at org.cryptomator.ui.unlock.UnlockWorkflow.attemptUnlock(UnlockWorkflow.java:100)

	at org.cryptomator.ui.unlock.UnlockWorkflow.call(UnlockWorkflow.java:81)

	at org.cryptomator.ui.unlock.UnlockWorkflow.call(UnlockWorkflow.java:44)

	at javafx.concurrent.Task$TaskCallable.call(Task.java:1425)

	at java.base/java.util.concurrent.FutureTask.run(Unknown Source)

	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)

	at java.base/java.util.concurrent.FutureTask.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)


Ok, cifs share was mounted read-only. for some reason cryptomator doesn’t like that? Anyways, that’s the fix :expressionless:

If you set your vault as “read-only” in the vault specific options, you don’t have to mount the share as writable (-;