You are not logged in.
I have TimeShift installed on my Arch laptop and it has worked without issue for months. Timeshift uses cronie to see if there is a backup to run, once an hour, on the hour. Around the end of August I started getting system mails that report errors from cronie. They come from the Timeshift task and include reference to 3 critical errors but the TimeShift task seems to complete successfully. I have a pacman hook to run TimeShift before doing a full system upgrade. This runs without reporting any errors. These are the errors from cronie when running TimeShift:
(process:5263): GLib-GIO-CRITICAL **: 22:00:01.735: g_file_get_path: assertion 'G_IS_FILE (file)' failed
** (process:5263): CRITICAL **: 22:00:01.735: tee_jee_file_system_path_combine: assertion 'path1 != NULL' failed
** (process:5263): CRITICAL **: 22:00:01.735: tee_jee_file_system_dir_exists: assertion 'dir_path != NULL' failedI've searched for possible causes and solutions but GLib-GIO-CRITICAL errors seem to crop up in a variety of scenarios and none of the solutions seem relevant to this issue. I would value any suggestions about how to fix this.
Last edited by PonJar (2020-09-18 18:20:50)
Offline
Could this error/warning indicating one of your backup path is non-existence, e.g dangling symlink.
Offline
I've found that I don't get these errors if I run TimeShift from the command line, which suggests the issue is something to do with the environment TimeShift sees when run by cronie.
I've also looked for broken symlinks as suggested by solskog. (Thank you) There were some, which I removed but nothing that seems to impact TimeShift paths. The hourly error messages continue. I'm thinking of deleting all my backups and reinstalling timeshift but will wait a while for any further comments
Offline