On Wed, 2021-03-17 at 21:31 -0500, Darrell Barabash wrote: > On Wed, 2021-03-17 at 16:20 -0500, Matt Connell wrote: > > My immediate guess is that cron doesn't know what X display to put > > evolution onto. > > SOLVED and thank you Matt. > > This was exactly the issue. I simply added "export DISPLAY=:0.0" at > the > beginning of the cron script and problem was solved. That also let me > use "notify-send" to put up a warning before shutting down. > > But, I'll probably put this on the back-burner. Regardless, I learned > a > very valuable lesson here for running cron scripts and do appreciate > the lesson. > > On Wed, 2021-03-17 at 22:22 +0000, Patrick O'Callaghan wrote: > > The wider problem is that (once again) we have to reiterate that > > evolution-backup, contrary to its name, *is not for taking periodic > > backups of Evolution data*. Its purpose is to help when moving > > accounts to a new machine, and it's designed to be run from the GUI > > (or at least from a user terminal). If you need to take a backup of > > Evolution, just use your normal user account backup system. > > Everything you need is already in your user account. That's all you > > have to do. > > Thanks for that sage advice Patrick. I was trying to just automate > the > "backup" button but understand that is not necessary nor desired. I > presume that in the case of needing a restoration, it would be > sufficient to simply restore the .local/share/evolution and the > .config/evolution folders?
In principle, yes. As regards restoring the messages, I prefer to keep everything on an IMAP server, but that's up to you. Restoring those folders should work either way. poc _______________________________________________ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
