I've never used DejaDup before, but since it's the default backup utility in Ubuntu Mate, I thought I'd give it a shot. Unfortunately, I can't get anywhere, because as soon as it starts a backup, it throws this error:
Traceback (innermost last):
File "/usr/bin/duplicity", line 1555, in <module>
File "/usr/bin/duplicity", line 1541, in with_tempdir
File "/usr/bin/duplicity", line 1393, in main
File "/usr/bin/duplicity", line 1511, in do_backup
File "/usr/bin/duplicity", line 572, in full_backup
File "/usr/bin/duplicity", line 454, in write_multivol
(tdp, dest_filename, vol_num)))
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 146, in schedule_task
return self.__run_synchronously(fn, params)
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 172, in __run_synchronously
ret = fn(*params)
File "/usr/bin/duplicity", line 453, in <lambda>
vol_num: put(tdp, dest_filename, vol_num),
File "/usr/bin/duplicity", line 342, in put
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 395, in inner_retry
% (n, e.__class__.__name__, util.uexc(e)))
File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 37: ordinal not in range(128)
Now, if I'm reading this right, it looks like it's trying to read the duplicity python scripts with ascii instead of unicode. Am I correct? If so, how would I rectify that?
Thanks in advance for any insight you can provide. Cheers!
I did a bit more digging, and found a bug for this on Deja Dup's launchpad page. It looks like this issue is affecting Ubuntu 18.04. Here's the link; if you're experiencing this issue as well, go to the bug report and let them know.
UPDATE 2: FOUND THE ISSUE
The folder I was trying to backup to "/var/backups/james" was owned by root, so DD didn't have permission to use it. chmod'd it back to my user and now it works like a charm. It was a permissions problem the whole time! Now, why that manifested itself as a unicode error is a total mystery to me. But I'll go update the bug file so that perhaps they can include a caveat in the code for providing a more informative error message when this is the case.