For me this bug was actually triggered by another new bug in lftp caused
by glibc upgate, see #1902832 which was obfuscated by this bug.
I found the patch from 19.04 disco which was mentioned in #19 which
fixed the unicode error for be and revealed the other bug.
https://launchpad.net/ubuntu/+sou
I have ubuntu 18.04 with ru locale and same issue
How I fixed it:
install snap versions
snap install duplicity --classic
snap install deja-dup --classic
remove apt version of deja-dup
sudo apt purge deja-dup
backup (option)
sudo mv duplicity duplicity_apt
link duplicity bin from snap p
Here's hoping a non-snap version gets fixed!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770929
Title:
Duplicity fails with UnicodeDecodeError in uexc function
To manage notifications about this
Hello all,
Apologies, I missed these recent messages.
For background, the error UnicodeDecodeError just means that a non-ASCII
character is hitting a piece of code that was not designed to handle it.
That is not surprising -- prior to the 0.8 series, very little of the
code was designed for non-A
I'm still experiencing this bug.
Backup failed. I can't find any processing logs, so I'm not able to know
which file caused the problem...
The dialog box shows:
Traceback (innermost last):
File "/usr/bin/duplicity", line 1555, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1541,
Hello,
in view of the above-mentioned post, it seems to me that the problem is not
fully solved and therefore I will describe my findings. Today I tried to set up
my small server backup to a second using duplicity package. I used some example
for writing tiny script.
#!/bin/bash
export PASSPHRA
Hello,
I receive the same error on Kubuntu 18.04, so I purge both duplicity 0.7
and deja-dup and install the snap version of them, as instructed by
Michael and Aaron. Nevertheless, I still get the same error when I run
"snap run duplicity". Here's the output:
$ which duplicity
/snap/bin/duplicit
To add on to Aaron's comment, if you are coming here because you hit
this bug while using deja-dup, you can install a version of deja-dup
that bundles in duplicity 0.8.0, which has the fix:
snap install deja-dup --classic --candidate
--
You received this bug notification because you are a member
All,
This should be fixed in 0.8.00, which has now been released. This is the
first 0.8-series release, so expect issues and test it out on data you
can afford to lose (if it comes to that).
I have now packaged up this version as a snap. You can install it by typing:
snap install duplicity --clas
** Changed in: duplicity
Assignee: Kenneth Loafman (kenneth-loafman) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770929
Title:
Duplicity fails with UnicodeDecodeError in uexc
All, to clarify the current position, this is fixed in the 0.8 series,
but I set out the steps to test the fix in comment #15 and was waiting
on testing feedback before merging the patch back into the 0.7 series.
Nobody gave me any testing feedback. It is therefore not yet fixed in
the 0.7 series.
** Changed in: duplicity
Status: Fix Committed => 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/1770929
Title:
Duplicity fails with UnicodeDecodeError in uexc function
To manage
I can also confirm that this is still happening with Ubuntu 16.04 LTS
duplicity-backup.sh v1.6.0
duplicity 0.7.19
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.6 LTS
Release:16.04
Codename: xenial
---[ Program versions ]---
Still, or again, appearing in 0.7.19
duplicity --version
duplicity 0.7.19
deja-dup --version
deja-dup 37.0
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.2 LTS
Release:18.04
Codename: bionic
Traceback (innermost last):
File "/u
This bug was fixed in the package duplicity - 0.7.18.2-1ubuntu3.1
---
duplicity (0.7.18.2-1ubuntu3.1) disco; urgency=medium
* debian/patches/bzr_unicode_error.patch:
- backport an upstream change to fix UnicodeDecodeError
(lp: #1770929)
-- Sebastien Bacher Fri, 12 Apr
Let's try to land the change in Ubuntu disco and see how it's going
there first before condidering SRUing
** Changed in: duplicity (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: duplicity (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because
Hello,
what is needed for the fix to land in ubuntu's duplicity package ? This bug has
bee fixed mainstream and the fix is available in other distro, so if any help
needed, please tell me where to start.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
** Changed in: duplicity
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770929
Title:
Duplicity fails with UnicodeDecodeError in uexc function
To manage
The 0.8-series was affected by this (as I mentioned above, fixing the
underlying problem avoids this error and a number of these have been
fixed, so it is harder to trigger).
I have just proposed a fix for it be merged into the 0.8-series:
https://code.launchpad.net/~aaron-whitehouse/duplicity/08-
** Branch linked: lp:~aaron-whitehouse/duplicity/08-uexc-fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770929
Title:
Duplicity fails with UnicodeDecodeError in uexc function
To manage notifica
Thank you everybody for your bug reports and comments.
I believe that this bug is already fixed in the 0.8-series, but we have
not yet released a package for this.
The code triggering this is used when there is an exception/error
message containing a non-ASCII character (for example a filename),
21 matches
Mail list logo
