You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
"Cancel" should either remove the partial snapshot or list it in the UI #554
Is your feature request related to a problem? Please describe.
When cancelling snapshot creation, files are left on the disk. Users wouldn't know, unless they check the snapshot directory.
Describe the solution you'd like
Simply remove the partially created snapshot on cancel.
Describe alternatives you've considered
List the partial snapshot in the UI somehow. This seems unnecessarily complex though.
Incomplete snapshots are automatically removed upon the next scheduled backup (which is run once an hour regardless of the user's scheduled backup settings), but that's unlikely to happen with users who only briefly plug in the backup disk to make a manual backup via the GUI, so I do agree that snapshots should be also cleaned up after a user clicks cancel.
I hit this on Timeshift 25.12.4 (Linux Mint 22.3, rsync mode), so I had a look at what happens to the folder afterwards.
After Cancel it stays in snapshots/, just without an info.json. After that, nothing shows it. timeshift --list prints only the other snapshots, and a freshly opened window shows the same. I also tried timeshift --delete --snapshot '<name>' on it, which answers Could not find snapshot, and as far as I can tell that is because SnapshotRepo.load_snapshots() puts a folder like this into invalid_snapshots while the listing and the delete only ever read snapshots.
The next hourly check then removed it on its own, as the comment above says it would, and its log shows Removing snapshots (incomplete): followed by Removed '2026-10-12_01-02-08'.
Personally I would not mind the partial copy being kept. I think it could still come in handy after a run that failed by itself. What bothers me is that I can neither see it nor remove it from within Timeshift.
Activity
FrostBird347 commentedon Jun 22, 2026
Incomplete snapshots are automatically removed upon the next scheduled backup (which is run once an hour regardless of the user's scheduled backup settings), but that's unlikely to happen with users who only briefly plug in the backup disk to make a manual backup via the GUI, so I do agree that snapshots should be also cleaned up after a user clicks cancel.
martin152 commentedon Oct 12, 2026
I hit this on Timeshift 25.12.4 (Linux Mint 22.3, rsync mode), so I had a look at what happens to the folder afterwards.
After Cancel it stays in
snapshots/, just without aninfo.json. After that, nothing shows it.timeshift --listprints only the other snapshots, and a freshly opened window shows the same. I also triedtimeshift --delete --snapshot '<name>'on it, which answersCould not find snapshot, and as far as I can tell that is becauseSnapshotRepo.load_snapshots()puts a folder like this intoinvalid_snapshotswhile the listing and the delete only ever readsnapshots.The next hourly check then removed it on its own, as the comment above says it would, and its log shows
Removing snapshots (incomplete):followed byRemoved '2026-10-12_01-02-08'.Personally I would not mind the partial copy being kept. I think it could still come in handy after a run that failed by itself. What bothers me is that I can neither see it nor remove it from within Timeshift.