Hmmmm. Many questions. The networked machine is an old desktop running a very old version of Ubuntu. There is no Windows involved here, and no mount so I'm not understanding where Samba comes into the picture. As I said in the original statement of the bug, I am connecting via the SSH protocol, so I am not entirely sure where the question of mounting a drive comes in. If I do mount a drive from the other machine, would this solve my problem and enable backups to finish, and if so, what protocol should I then set up duplicity to use? Or would another of the available duplicity protocols work better for me?
Even more puzzling, a directory listing of the troublesome file shows it is < 2GB in size by a factor of 16 or so: -rw-rw-r-- 1 scohen scohen 262180864 Oct 7 2021 duplicity-full- signatures.20211007T135951Z.sigtar.gz I suppose truncation might have occurred to a size well < 2GB. Also, why is this file so big? In looking over the earlier output, I appear to be backing up a lot of old junk that no longer requires backup or even existence. Would eliminating some of it help me? Or, since I have no need of earlier backups, might I be well served by simply erasing everything in the Taormina directory of the backup drive and starting over? Thanks. -- 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: Invalid Status in duplicity package in Ubuntu: Invalid 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
