UnicodeDecodeError when backing up to Ubuntu One in some locales
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Duplicity |
Fix Released
|
Medium
|
Unassigned | ||
duplicity (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Quantal |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
Most non-English users cannot back up to Ubuntu One (the default in Deja Dup) at all.
When backing up to Ubuntu One, the duplicity Ubuntu One backend will return unicode filenames. This can cause UnicodeDecodeErrors in some locales when mixed with duplicity's UTF-8 translated strings.
For example, pt_BR is affected because it uses non-ascii characters.
As for Ubuntu, Quantal and Raring are affected. Precise and below don't seem to care.
[Test Case]
sudo apt-get install language-
LANGUAGE=pt_BR duplicity --no-encryption /bin u1+http://
[Fix]
In u1backend.py, an ".encode('utf-8')" needs to be added in the list() function.
https:/
[Exception]
Traceback (most recent call last):
File "/usr/bin/
with_
File "/usr/bin/
fn()
File "/usr/bin/
globals.
File "/usr/lib/
self.
File "/usr/lib/
map(
File "/usr/lib/
log.
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 4: ordinal not in range(128)
Related branches
- duplicity-team: Pending requested
-
Diff: 12 lines (+1/-1)1 file modifiedduplicity/backends/u1backend.py (+1/-1)
description: | updated |
summary: |
- UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 4: - ordinal not in range(128) + UnicodeDecodeError when backing up to Ubuntu One in some locales |
description: | updated |
description: | updated |
affects: | deja-dup → duplicity |
affects: | deja-dup (Ubuntu) → duplicity (Ubuntu) |
description: | updated |
description: | updated |
description: | updated |
tags: |
added: verification-done removed: verification-needed |
Changed in duplicity: | |
status: | New → Fix Committed |
Changed in duplicity: | |
milestone: | none → 0.6.21 |
status: | Fix Committed → Fix Released |
importance: | Undecided → Medium |
Status changed to 'Confirmed' because the bug affects multiple users.