Bug 387543 - Vault randomly disables
Summary: Vault randomly disables
Status: RESOLVED WORKSFORME
Alias: None
Product: Plasma Vault
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Ivan Čukić
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2017-12-03 05:22 UTC by Ivan S
Modified: 2018-10-29 02:23 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ivan S 2017-12-03 05:22:11 UTC
I put several hundred gigabytes of files into a cryfs vault and a few hours later the vault no longer appeared in the Vaults applet.

I checked ~/.config/plasmavaultrc and it listed the vault as "[path-to-vault-redacted]=false"

Is this a bug, or is there some reason why large vaults are auto-disabled?
Comment 1 Ivan Čukić 2017-12-04 09:13:51 UTC
Where have you placed the vault path and the mount path?
Comment 2 Ivan S 2017-12-04 15:11:58 UTC
(In reply to Ivan Čukić from comment #1)
> Where have you placed the vault path and the mount path?

Defaults: ~/Vaults/crypthome, ~/.vaults/crypthome.enc
By the way, it seems this isn't just a problem with large vaults, on a new account the same thing occurred with the first vault I created.
Comment 3 Ivan Čukić 2018-01-10 12:42:33 UTC
I was unable to reproduce the issue.

In order to get some info, I've put a small debugging feature in the next release (5.12 - beta should arrive on Jan 15th).

When you reproduce the issue with the new release, post the value of 'lastError' variable from the plasmavaultrs file for the disabled vault and reopen this issue.

I hope this will give enough info to track down the bug.
Comment 4 Andrew Crouthamel 2018-09-28 03:38:07 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Andrew Crouthamel 2018-10-29 02:23:56 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!