Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Timeshift not making scheduled snapshots #396

Aesyir opened this issue Mar 9, 2019 · 2 comments


Copy link

@Aesyir Aesyir commented Mar 9, 2019

Timeshift is not making scheduled snapshots, I set it to make daily snapshots and it does not do them, I checked /etc/cron.d/ and all I found was "timeshift-hourly" I tried "crontab -l" and it just said that this user has no crontab. I have cronie installed (arch linux) is there some other dependency I am missing?

EDIT: I did realize timeshift always checks hourly to see when a snapshot is scheduled so that explains why there is only "timeshift-hourly". in the end though It is still not doing scheduled snapshots at all.


This comment has been minimized.

Copy link

@BillFleming BillFleming commented Mar 10, 2019

On my arch machines after some research I saw the schedules WERE being setup correctly, but the chron service wasn't enabled or running. As soon as I enabled it the scheduled snapshots started working. (I had installed from AUR.)

systemctl enable cronie.service 
systemctl start cronie.service 

Once you start it the jobs in /etc/cron.d should start running.
Next up is to check that the command is actually working correctly. After you setup timeshift if you run for example "sudo timeshift --check --scripted" from command line it should auto create a snapshot (with appropriate flags) if one is due. Then run the timeshift GUI afterwords to easily confirm the new snapshot is present. If this command doesn't work then the problem is somewhere in the settings for timeshift or user account/permission problem.


This comment has been minimized.

Copy link

@Aesyir Aesyir commented Mar 10, 2019

It seems the cronie service was not started! I would have thought the service was already started but I guess not! thanks for the help.

@Aesyir Aesyir closed this Mar 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
2 participants
You can’t perform that action at this time.