Closed ronohara closed 1 month ago
Ok - found the issue. In the 'check.py' file (line 200) there is a hard coded location for tying to find the timeshift executable. (/usr/bin/timeshift)
On my system, I was debugging a timeshift problem about a year ago and installed from source so that I could debug the issue. Compiling from source puts the executables into /usr/local/bin.
I will revert to the distribution version of timeshift.
The error messages could reflect the supposedly missing executable ... but since actually running timeshift only needs it to be found in the path perhaps it could use 'which' to see if timeshift is available rather than a hard coded path
Resolved by using the distribution version of timeshift
I just took a manual Timeshift backup. The backup medium is a USB drive which is mounted when the Running check 'System snapshots process occurs ... so the backup should be detected.
The Timeshift backup needs to be on an external USB drive to have adequate space
EDIT
I changed the Timeshift setup to only backup the system (not user areas) using the internal disk as the backup location - IE the default setup of Timeshift. I then took a fresh backup .... but the error remains the same.