Comment 4 for bug 1980908

Hi, Kenneth! This would almost certainly just be Deja Dup's fault, I can't imagine duplicity would be an issue here.

@khteh - it should be safe to kill an active duplicity process and restart your backup, to recover from this happening as a workaround. But obviously, there's still the bug that it did happen in the first place.

How did you close Deja Dup? Normally, there's the progress dialog with cancel or resume later buttons, both of which should stop the duplicity process. If Deja Dup was shut down unexpectedly, I could maybe see this happening.