https://bugs.kde.org/show_bug.cgi?id=488573
Nate Graham <n...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |n...@kde.org
Ever confirmed|0 |1
Status|REPORTED |CONFIRMED
Summary|Vaults manually deleted on |Better handling for cases
|disk are grayed out and can |where the plasmavaultrc or
|not be removed via applet |vault data files are
| |missing for whatever reason
Severity|normal |wishlist
--- Comment #1 from Nate Graham <n...@kde.org> ---
This is user error: if you're going to go poking around and manually delete the
data files, you need to delete the references to them in the config file too.
Anyone not enough of a technical expert to know that probably shouldn't be
manually deleting stuff from ~/.local/share/!
...But that's not the world we live in, so it's probably reasonable to handle
these cases. Another example came up today where a person failed to copy all
the files over properly during a restore-from-backup.
So IMO these are the cases it would make sense to handle:
Data files are missing, but plasmavaultrc file exists:
- Show a message in the UI that the vault got broken because its data was
deleted. Advise the user to recover it from backup, showing the past that
Vaults expects to find it at. Also offer a "delete vault" button they can use
to clear the entry and start over if the data files were removed intentionally,
or no backup is available.
plasmavaultrc file is missing, but the data files exist:
- Recreate the data that would exist in plasmavaultrc based on the names of the
data files
--
You are receiving this mail because:
You are watching all bug changes.
