*** If it happens that a sudo apt autopurge is performed kde vaults stop working If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Please remove this comment after reading and before submitting - thanks! *** SUMMARY encfs and cryfs are marked as purgeable in kde neon once plasma 6.4.0 is installed and if a "sudo apt autopurge" is performed, then kde vaults stop working (perhaps apt autoremove also, but couldn't try) STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: Neon KDE Plasma Version: 6.4.0 KDE Frameworks Version: 6.15.0 Qt Version: 6.9.0 ADDITIONAL INFORMATION
in 6.4.0 plasma vaults switched to supporting only gocryptfs, commit https://invent.kde.org/neon/kde/plasma-vault/-/commit/899153ec01a457f240506723416711d261fccfe1 reflects those changes in runtime dependencies
Plasma Vault supports all backends it used to, it doesn't support **creating** new vaults with backends other than gocryptfs anymore (for the time being - might change in the future) Removing encfs/cryfs packages makes previously created vaults inaccessible to the users which is a serious bug on Neon's part.
Git commit 93288f22b3d99e3ea5c7ea603d67120de591e52d by Carlos De Maine. Committed on 12/07/2025 at 08:32. Pushed by carlosdem into branch 'Neon/release'. bring back cryfs & encfs as runtime deps as existing vaults can still be used but not created with M +3 -1 debian/control https://invent.kde.org/neon/kde/plasma-vault/-/commit/93288f22b3d99e3ea5c7ea603d67120de591e52d