Status and check-tab missing
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Déjà Dup |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
There is no method to manually trigger check of completeness and integrity of archive.
It is sometimes done in background ( https:/
State directly after install.
lsb_release -d
Description: Ubuntu 14.04.4 LTS
dpkg-query -W deja-dup duplicity
deja-dup 30.0-0ubuntu4
duplicity 0.6.23-1ubuntu4.1
file created by gsettings list-recursively org.gnome.DejaDup > /tmp/deja-
org.gnome.DejaDup last-restore ''
org.gnome.DejaDup periodic false
org.gnome.DejaDup full-backup-period 90
org.gnome.DejaDup backend 'file'
org.gnome.DejaDup last-run ''
org.gnome.DejaDup nag-check ''
org.gnome.DejaDup prompt-check ''
org.gnome.DejaDup root-prompt true
org.gnome.DejaDup include-list ['$HOME']
org.gnome.DejaDup exclude-list ['/home/
org.gnome.DejaDup last-backup ''
org.gnome.DejaDup periodic-period 7
org.gnome.DejaDup delete-after 0
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
See my comment #5 about a possible CLI solution on the bug report you linked to.
As for an actual way of triggering a verification through the GUI, I'm not sure it is worth it since it adds clutter in the interface, a verification is run after each backup and a more complete one every two months, and it could make an average user think the backup solution is unreliable and the backups it makes need regular checking.