Failure during backup, probably bad path name

Bug #1049375 reported by Sidnei da Silva
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
duplicity (Ubuntu)
New
Undecided
Unassigned

Bug Description

Traceback (most recent call last):
  File "/usr/bin/duplicity", line 1403, in <module>
    with_tempdir(main)
  File "/usr/bin/duplicity", line 1396, in with_tempdir
    fn()
  File "/usr/bin/duplicity", line 1378, in main
    incremental_backup(sig_chain)
  File "/usr/bin/duplicity", line 563, in incremental_backup
    bytes_written = dummy_backup(tarblock_iter)
  File "/usr/bin/duplicity", line 197, in dummy_backup
    while tarblock_iter.next():
  File "/usr/lib/python2.7/dist-packages/duplicity/diffdir.py", line 507, in next
    result = self.process(self.input_iter.next(), size)
  File "/usr/lib/python2.7/dist-packages/duplicity/diffdir.py", line 188, in get_delta_iter
    for new_path, sig_path in collated:
  File "/usr/lib/python2.7/dist-packages/duplicity/diffdir.py", line 267, in collate2iters
    relem1 = riter1.next()
  File "/usr/lib/python2.7/dist-packages/duplicity/selection.py", line 187, in Iterate
    log.Debug(_("Selecting %s") % subpath.name)
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 72: ordinal not in range(128)

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: duplicity 0.6.19-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
Uname: Linux 3.5.0-13-generic x86_64
ApportVersion: 2.5.1-0ubuntu7
Architecture: amd64
Date: Tue Sep 11 18:31:26 2012
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120901)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: duplicity
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Sidnei da Silva (sidnei) wrote :
Revision history for this message
Michael Terry (mterry) wrote :

Thank you for the report! This looks like bug 989496, so I'll mark it as a duplicate. I'm looking into the issue.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.