Re: bug: deja-dup not working any more & crashes on every startup since two weeks

[inderaue23 arcor de]

DEJA_DUP_DEBUG=1 deja-dup --backup | tail -n 1000 > /tmp/deja-dup.log
gives me a really huge output. as i don't understand the logs, i really don't not which parts 
a) do you need/are interesting for working on it and b) i have no clue where to scrub the log of any sensible details - maybe you can help here?!

all the best ANNA

Vej <ubuntu jonasdiekmann de> hat am 13. April 2018 um 22:15 geschrieben:

Hello Anna.

This looks like a bug, which should be fixed long ago and reappeared recently.

Could you provide us with the following information please?

1. The version of deja-dup and duplicity:
    (if on Ubuntu or Debian:)
    dpkg-query -W deja-dup duplicity

    (if on Fedora or other RPM-based systems:)
    rpm -q deja-dup duplicity

2. The file /tmp/deja-dup.gsettings after running the following line (you may want to scrub the file of any incriminating file names or details):
    gsettings list-recursively org.gnome.DejaDup > /tmp/deja-dup.gsettings

3. The file /tmp/deja-dup.log after running the line below and replicating the problem (you may want to scrub the log of any incriminating file names or details):

    DEJA_DUP_DEBUG=1 deja-dup --backup | tail -n 1000 > /tmp/deja-dup.log

Best regards

Vej


Btw: There seems to be an existing bugreport for this: https://bugs.launchpad.net/deja-dup/+bug/1736164.
So instead of mailing the requested information to us, you could add it there.



Am 12.04.2018 um 10:51 schrieb inderaue23 arcor de:

Hej there, i remeber there was a duplicity update a few weeks? ago.

Today i tried deja dup and it always give me the following error with my always used external usb stick.

there is plenty of space left. Maybe the Traceback could help here!? Iam running 37.1-1.fc27.x86_64 on Fedora 27.

all the best Anna

*First issues informations are provided within deja-dup itself, the second one is the constantly crash ABRT server is showing on every system startup since two weeks now with "Backup Monitor quit unexpectedly" Any idea?

Traceback (innermost last):
File "/usr/bin/duplicity", line 1555, in <module>
with_tempdir(main)
File "/usr/bin/duplicity", line 1541, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1393, in main
do_backup(action)
File "/usr/bin/duplicity", line 1414, in do_backup
sync_archive()
File "/usr/bin/duplicity", line 1204, in sync_archive
copy_to_local(fn)
File "/usr/bin/duplicity", line 1146, in copy_to_local
fileobj = globals.backend.get_fileobj_read(fn)
File "/usr/lib64/python2.7/site-packages/duplicity/backend.py", line 676, in get_fileobj_read
self.get(filename, tdp)
File "/usr/lib64/python2.7/site-packages/duplicity/backend.py", line 395, in inner_retry
% (n, e.__class__.__name__, util.uexc(e)))
File "/usr/lib64/python2.7/site-packages/duplicity/util.py", line 79, in uexc
return ufn(unicode(e).encode('utf-8'))
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 21: ordinal not in range(128)