I’ve been running timeshift for some time now but a week ago I installed ssmtp to report on a new cron job. To my surprise I bagan getting timeshift errors, every hour on the hour. At the correct timeshift backup time I got the errors plus the timeshift action report. I’m still getting them.
(process:2251972): GLib-GIO-CRITICAL **: 11:00:01.743: g_file_get_path: assertion 'G_IS_FILE (file)' failed ** (process:2251972): CRITICAL **: 11:00:01.744: tee_jee_file_system_path_combine: assertion 'path1 != NULL' failed ** (process:2251972): CRITICAL **: 11:00:01.744: tee_jee_file_system_dir_exists: assertion 'dir_path != NULL' failed /dev/sde1 is mounted at: /run/timeshift/backup, options: rw,relatime Daily snapshots are enabled Last daily snapshot is 15 hours old
I assume I’ve been getting these errors for the past gods-know how many months. Perhaps timeshift should have an email setup option, as luckyBackup does, that would perhaps auto-install a simple mail server such as ssmtp or sendEmail and make it clear that this was required.
Anyway, I found a recommendation on this (old) forum to edit the file /etc/sddm.conf and delete DefaultPath. I cannot find sddm.conf so this is not a solution. Help, please?
ALSO: On the Schedule tab of timeshift there is the message: “Snapshot device not selected”. This is either wrong or refers to something other than the device to which timeshift is daily backing up my system. Again, Help, please?
What happens if (as in my current instance) the original backup drive dies and the snapshots are assigned to a new one? Is the complete restore compromised or is there sufficient intormation in the later snapshots to restore correctly?
One other thing: there is no option I can find that allows me to change the daily backup time from 20:00 (when I am using the computer) to something like 03:00 (when I am not).