I can confirm that the work-around in comment 16 does work, although I had to add this to my backup script:
export LANG=en_US.utf8 export LANGUAGE= export LC_CTYPE="en_US.utf8" export LC_NUMERIC="en_US.utf8" export LC_TIME="en_US.utf8" export LC_COLLATE="en_US.utf8" export LC_MONETARY="en_US.utf8" export LC_MESSAGES="en_US.utf8" export LC_PAPER=en_US.UTF-8 export LC_NAME="en_US.utf8" export LC_ADDRESS="en_US.utf8" export LC_TELEPHONE="en_US.utf8" export LC_MEASUREMENT="en_US.utf8" export LC_IDENTIFICATION="en_US.utf8" export LC_ALL= Another locale that can be used to reproduce the problem is fr_CA.utf8. So this bug has in fact nothing to do with filenames and everything to do with the localized error messages breaking duplicity. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1050509 Title: Duplicity doesn't handle non-utf8 filenames well To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1050509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
