Since I feel like I corrupted something on the update or when I nuked my aplet I did the fresh install and everything is tuned and back where I wanted it. Thanks everyone who tried to help! Lesson and other new info learned!
3 Likes
The lesson you should take away from this is that keeping up to date backups will save you a lot of frustration and heartbreak when sh*t goes sideways for whatever reason.
Snapshots are not the same as backups.
4 Likes
Backups saved me - thatās how Iām up and running so fast. Lost no data because I understand fully that snapshots and backups are not the same. I was coaxed into cleaning up my āold snapshotsā by the garuda health messages and it cleaned everything older than 24 hours. Big mistake. Also, nuking the ~/.config/plasma-org.kde.plasma.desktop-appletsrc will never happen again.
The actual lesson: Donāt blindly follow system health cleanup recommendations. Those snapshots might be your only rollback option when things go sideways.
What I learned:
-
The plasma desktop config file is THE critical file for your entire desktop layout
-
When corruption gets deep enough (calendar loading āholidayseventsā letter by letter), just reinstall. Plasma wouldnāt even create a new
plasma-org.kde.plasma.desktop-appletsrc! -
Fresh install: 30 minutes. Trying to undo mass corruption: potentially days
Sometimes the nuclear option is the smart option.
1 Like
I use only a 120 GB SSD as my boot drive, but I usually set my snapshot retention to 80 - 85. I symlink all my data drives into my home directory, so my boot drive still usually has lots of space. I simply keep a close watch on my frees space and itās a pretty frugal use of space on my boot drive.
You can never keep too many snapshots IMO.
5 Likes
Borg/Vorta = my life raft in this instance. Iām new to Arch/Garuda (less than a year), hadnāt even looked into snapshot retention settings. Going to change that now.
I have a full TB for home and root, plus another NVMe Iām adding next week (was going to be this weekend!). Iām going to start with these retention settings and adjust as needed:
NUMBER_LIMIT=20
TIMELINE_LIMIT_HOURLY=5
TIMELINE_LIMIT_DAILY=7
TIMELINE_LIMIT_WEEKLY=4
TIMELINE_LIMIT_MONTHLY=6
TIMELINE_LIMIT_YEARLY=2
This should give me plenty of snapshots total without triggering cleanup warnings. With external backups via Borg/Vorta plus proper snapshot retention, Iāll have both local rollback and disaster recovery covered.
1 Like
That should not be the takeaway here.
Those only show up in garuda-health if you have 1. old ārootsā from previously restored snapshots or 2. manual snapshots older than 14 days.
4 Likes
Weāll have to agree to disagree here. The statement was about āblindlyā following recommendations, and thatās definitely ONE of my multiple takeaways from this situation.
Iām now digging into snapper settings - specifically looking to disable cleanup warnings for manual snapshots since I donāt ever want those flagged for removal. My snapshot strategy will be more organized and robust going forward.
I should have researched what garuda-healthās cleanup recommendation would actually do before acting on it. Thatās on me and one of multiple valid takeaway Iām taking from this experience.
Hello there,
I can see that this issue is resolved, but i fail to see what the solution was. Could you please share the steps you took to resolve it? Or was it a fresh install as you said on your latest comments?
I do have a similar issue as posted here Desktop randomly restarts
After looking more into it, i have concluded that Wayland is still unstable with NVIDIA drivers which seems to have a lot of issues occuring due to that combination. I do have NVIDIA on my Lenovo Ideapad 3 Gaming and the issue you are stating here in your comment is exactly the behavior i get.
Thank you very much in advance
1 Like
I engaged you in your own thread.
1 Like
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.