https://bugs.kde.org/show_bug.cgi?id=485151
--- Comment #3 from k...@maillama.com --- Two things: 1. I noticed that the out of memory error doesn't always occur. I just updated the system and restarted and afterwards it still wouldn't let me unlock the vault, but there was no error in DMESG as listed above. 2. I was able to find a workaround. By going into "Configure Vault" and changing the mount point to a new, empty folder, the vault now unlocks correctly. I'm wondering if this "error" was caused by me copying something in the mount point folder. If so, it would be better usability to list the mountpoint in the error so people knew where to look, eg, instead of: "Failed to open: The mount point directory is not empty, refusing to open the vault" Maybe: "The vault's mount point is not empty, so it can't be opened. Please check /path/to/mount/point is empty" -- You are receiving this mail because: You are watching all bug changes.
