Bug 422836

Summary:	Vaults don't open, even though dolphin launches there
Product:	[Unmaintained] Plasma Vault	Reporter:	David <david.cortes.rivera>
Component:	general	Assignee:	Ivan Čukić <ivan.cukic>
Status:	RESOLVED UPSTREAM
Severity:	major
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Debian testing
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description David 2020-06-11 17:19:30 UTC

SUMMARY
After updating to KDE frameworks 5.70, whenever I open a vault from the system tray icon, it asks me for the password, and launches a dolphin instance pointing to the path in which the vault should be opened, but the vault is not opened - i.e. it doesn't show any files in the folder, and clicking again on the system tray doesn't show it as being open.

STEPS TO REPRODUCE
1. Set up some encrypted vault, add files to it.
2. Upgrade to frameworks 5.70.
3. Restart computer.
4. Open vault from the system tray.

OBSERVED RESULT
Should open the vault.

EXPECTED RESULT
Vault is not opened, even though dolphin is launched pointing to the folder in which the vault files should appear.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.17.5
KDE Frameworks Version: 5.70
Qt Version: 5.12.5

ADDITIONAL INFORMATION

Comment 1 David 2020-06-11 17:24:24 UTC

Using `cryfs` from the command line shows this:
Deriving encryption key (this can take some time)...done
[2020-06-11 20:23:15.585] [Log] [error] Crashed: Deserialization failed - size overflow

Comment 2 Ivan Čukić 2020-06-12 13:03:46 UTC

Hi, you should open a bug report on cryfs [1] as it is issue in it.

There is a possibility that the underlying file system was corrupted so the cryfs key can not be opened, but cryfs maintainers will know the cause and the potential fix better than I.

[1] https://github.com/cryfs/cryfs/issues