I'm very confused though that this affects just Deja Dup restores, not duplicity ones. Perhaps the cache directory is causing problems (duplicity and deja-dup use different cache locations).
For anyone that still has a backup set that reliably hits this bug, try the following:
mv ~/.cache/deja-dup ~/.cache/deja-dup.old
And try restoring again. I'm curious if that gets around the problem.
Note that rdiff-backup apparently has hit this issue enough to have an FAQ entry about it: http:// www.nongnu. org/rdiff- backup/ FAQ.html# crc
I'm very confused though that this affects just Deja Dup restores, not duplicity ones. Perhaps the cache directory is causing problems (duplicity and deja-dup use different cache locations).
For anyone that still has a backup set that reliably hits this bug, try the following:
mv ~/.cache/deja-dup ~/.cache/ deja-dup. old
And try restoring again. I'm curious if that gets around the problem.