https://bugs.kde.org/show_bug.cgi?id=386200
--- Comment #30 from Ivan Čukić <ivan.cu...@kde.org> --- Hi medin, First, I'd create a backup of the encrypted data just in case. Next, mount the vault manually from terminal. BACKEND_COMMAND ABSOLUTE_PATH_TO_ENCRYPTED_DATA WHERE_YOU_WANT_TO_MOUNT Depending on which backend you used to create the vault, BACKEND_COMMAND will be cryfs, encfs or gocryptfs. So, for example, if you used encfs and your vault data is in /home/user/.local/share/plasma-vault/VaultName.enc and you want to mount it to /home/user/vaults/VaultName, you'd do this: encfs /home/user/.local/share/plasma-vault/VaultName.enc /home/user/vaults/VaultName You'll be able to access the unlocked data in /home/user/vaults/VaultName. You can copy the data somewhere (for example, to a new Vault you created). To close/unmount the vault, just do fusermount -u /home/user/vaults/VaultName If you want to test out the (hidden) import feature, after all of the steps above (including the call to fusermount -u), do: qdbus org.kde.kded5 /modules/plasmavault requestImportVault And go through the steps of importing the vault. Please report back if it worked. -- You are receiving this mail because: You are watching all bug changes.
