Thinking a little more about what I've been able to observe, I suspect that deja-dup is launching a fresh duplicity backup while the previous one is still running due to some sort of lock fail, or assumption that the former job couldn't possibly still be running. This new process cleans up, removing the partially completed backup and files required by the first instance, cause the first instance to abort when it tries to access these resources. deja-dup doesn't notice because it is dealing with the new duplicity job and couldn't care less about what is happening with the first instance.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1210499 Title: Fresh backup started rather than current backup resumed, backups never complete To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1210499/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
