I'm in the same boat. LTS 14.04, reset dconf and deleting .cache/deja-dup didn't help..
Also, I've observed an odd behavior: In my case, it doesn't actually backup anything. It starts a fresh backup (when I've reset everything), and after some seconds skips to "verifying" directly, without having done a backup. Paths are OK; my user home is quite big. I don't know if I'm the only one having this behavior?
If somehow deja-dup isn't able to backup anything, it also makes sense that it doesn't find the .cache-test-file in the backup of course ;-)
Important: In my case, my whole /home/[user] is a bind mount (`mount -o bind`) to another disk - could that be an issue?
** Is there any way to get the duplicity commands what deja-dup is using, or any other method to know what it's actually doing? Any way to see under the GUI? Any logs, any --verbose switch? (didn't see any..?)
I'm in the same boat. LTS 14.04, reset dconf and deleting .cache/deja-dup didn't help..
Also, I've observed an odd behavior: In my case, it doesn't actually backup anything. It starts a fresh backup (when I've reset everything), and after some seconds skips to "verifying" directly, without having done a backup. Paths are OK; my user home is quite big. I don't know if I'm the only one having this behavior?
If somehow deja-dup isn't able to backup anything, it also makes sense that it doesn't find the .cache-test-file in the backup of course ;-)
Important: In my case, my whole /home/[user] is a bind mount (`mount -o bind`) to another disk - could that be an issue?
** Is there any way to get the duplicity commands what deja-dup is using, or any other method to know what it's actually doing? Any way to see under the GUI? Any logs, any --verbose switch? (didn't see any..?)