Kenneth: First, thank you!
I don't run duplicity via the command line. I run it using the Ubuntu GUI app "Backups" which I believe is just a gui-name for deja-dup. In that setup I have a saved Preferences which governs how the Backup is done, which files/directories to back up, which to exclude, where to send the backup, etc. Trying duplicity -v9 fails with $ duplicity -v9 Command line error: Expected 2 args, got 0 Enter 'duplicity --help' for help screen. Evidently, the deja-dup app is saving this information in a config file somewhere and then building a command line to send to duplicity. I don't see how to invoke duplicity so as to use these config files, whose location I don't know either. So, next step is to try to invoke the debugging via a deja-dup command line. I try this (per deja-dup --help): $deja-dup --gtk-debug=9 > log and it starts the GUI, producing the same failure message; however nothing is appended to the log file, so evidently --gtk-debug=9 in deja-dup is not equivalent to duplicity -v9. Finally, using the Google, I find that the way to turn logging on for deja-dup is DEJA_DUP_DEBUG=1 deja-dup Redirecting this to log does indeed produce a massive file. Hopefully, this is what you are looking for. If not please let me know how to 1) run duplicity so that my deja-dup preferences are used or 2) run deja-dup to produce the input you want. log head and tail will be attached. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1970124 Title: duplicity backup fails with obscure error message Ubuntu 22.04 Status in Duplicity: New Status in duplicity package in Ubuntu: New Bug description: I try to do a backup onto a network location (ssh://192.168.1.61 - I can successfully connect to this location via ssh). The backup completes the scan phase, then dies with error messages like this: Failed to read /tmp/duplicity-xdksj47v-tempdir/mktemp-_5khubio-2: (<class 'EOFError'>, EOFError('Compressed file ended before the end- of-stream marker was reached'), <traceback object at 0x7f5f660da740>) While the backup is running, we can see a duplicity* directory under /tmp: $ ll /tmp/duplicity-i6olpr17-tempdir/ total 16 drwx------ 2 scohen scohen 4096 Apr 24 12:52 ./ drwxrwxrwt 26 root root 12288 Apr 24 12:52 ../ -rw------- 1 scohen scohen 0 Apr 24 12:52 mkstemp-cx21bs8l-1 However, note that this is not the directory mentioned in the failure message. A scan of the directory after the failure reveals no files like /tmp/dupl* Why is it trying to read files that do not exist? $ lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 $ apt-cache policy duplicity duplicity: Installed: 0.8.21-1build1 Candidate: 0.8.21-1build1 Version table: *** 0.8.21-1build1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1970124/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
