It may or may not be related, but before seeing this bug, I had run
restore in a loop on different times, asynchronously, that is to say I
used:
for x in `seq 10 15`
duplicity --time {$x}D ... &
Note the ampersand, I forked them to a background process.
THEN on top of that I hit CTRL-C to force a cancel. This may have corrupted a
cache.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/498933
Title:
Crash when restoring data KeyError
To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/498933/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
