| Summary: | Allow to restore full plasma config from checkpoints | ||
|---|---|---|---|
| Product: | [Unmaintained] plasma4 | Reporter: | anton <benderamp> |
| Component: | general | Assignee: | Plasma Bugs List <plasma-bugs> |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | wishlist | CC: | diego.ml, finex |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
anton
2009-07-15 18:59:53 UTC
It should be interesting a backup of the whole ~/.kde directory, not only plasma settings. Probably a simpler solution (almost without UI) might be making plasma save/load config algorithm more reliable. When save: 1. Copy existing plasmarc config file to something like plasmarc-bakXXX2 2. Only after that rewrite existing plasmarc file 3. Remove previous plasmarc-bakXXX1 file (previous backup file) - only after making sure the new config is completely safe in 2 files. Do not perform 2nd and 3rd steps if the 1st one fails - most likely the new file will not be successfully created too - this might easily happen for example if there is no free space in /home directory. If there were a problem on the 1st or the 2nd step, show warning dialog to user "Failed to save plasma config" and 2 buttons "Retry" and "Cancel", so the user would be able to go to file manager and free few bytes in his home dir or something. When load: 1. First try plasmarc file as usual 2. If failed to load (file is missing or zero length or corrupted) try the most recent backup file (plasmarc-bakXXX2) instead. 3. Only if there were no backup file or even it is corrupted create new default plasmarc file. As I can see, with such algorithm at least one copy of the most recent successful plasma config file would always be safe even if something evil would happen during the save process. This might also be applied to other apps - for example I remember problems on my old kde3 desktop with desktop sessions - I had "save session on logout" option set and several times I did logout when my /home directory did not have any free space on it - kde tried to save its session and failed, but before it failed it did kill the old session file, so on login I received empty desktop and had to reopen all applications again (the worst thing is multiple konqueror windows with multiple tabs with different sites on each). It could be interesting to see something similar to what is being done for the panel: http://aseigo.blogspot.com/2010/04/solving-little-problem-with-slightly.html Hello! This feature request was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this feature request is already implemented in Plasma 5, or is no longer applicable. Accordingly, we hope you understand why we must close this feature request. If the requested feature is still desired but not implemented in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging Thanks for your understanding! Nate Graham |