This is generically true -- we do report errors from duplicity. So I'll
mark this fix released.
There are some rare errors where duplicity just crashes which Deja Dup
doesn't report because duplicity didn't tell us about it (you hit one of
these errors). In such cases, it's not clear which part of the
duplicity log to report to the user (full log is too enormous). I
generally need to see the log to understand why duplicity bailed, so
more action is required from user.
** Changed in: deja-dup (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/599197
Title:
deja-dup does not report underlying duplicity errors
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
