Andreas Klust wrote (#18) > I was able to track the problem down to one file in my home directory with a > character that is not conforming to UTF-8.
I wonder if you could share how you found out the files that Duplicity chokes on? After having my backup -system disfunctional for two months, i would love to rename some files as a workaround to the bug. Duplicity itself (well, i use Deja-Dup interface) gives just an "unknown error" and the details don't unfortunately pin it down to which character string is causing the conflict. Cheers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/989496 Title: UnicodeDecodeError: 'utf8' codec can't decode byte 0xd1 in position 117 To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/989496/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
