Comment 0 for bug 1778638

I am using Duplicity through Deja-Dup through its deja-dup-monitor process. After update to Bionic, it has basically stopped doing backups. Version is duplicity 0.7.17+bzr1357, Python version is 2.7.15rc1, Xubuntu Bionic.

It seems to be stuck in pipes related call. When I try to strace the process I get this:

strace: Process 28490 attached
splice(9, [359], 16, NULL, 1048576, SPLICE_F_MORE

From handle 9 to 16. The handle 9 is a file on my CIFS mount to where I do backups. If I go to the directory and do ls it works fine:

duplicity 28490 USER 9r REG 0,52 359 67128742 /var/backups/USER/backup.HOST/duplicity-inc.20180611T014226Z.to.20180612T014125Z.manifest.gpg

Handle 16 is a pipe:

duplicity 28490 USER 16w FIFO 0,12 0t0 1415081 pipe

But I do not see anyone reading from it. That sounds like the issue.

It seems to be stuck in GIO file handling code:

(gdb) bt
#0 0x00007f0e78588dda in splice (fd_in=9, off_in=0x7ffe5e958388, fd_out=16, off_out=0x0, len=1048576, flags=4) at ../sysdeps/unix/sysv/linux/splice.c:26
#1 0x00007f0e6ee2672e in () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#2 0x00007f0e6ee2d827 in g_file_copy () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#3 0x00007f0e76ccfdae in ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
#4 0x00007f0e76ccf71f in ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
#5 0x00007f0e6fb8ecfa in () at /usr/lib/python2.7/dist-packages/gi/_gi.x86_64-linux-gnu.so
#6 0x00007f0e6fb908e8 in () at /usr/lib/python2.7/dist-packages/gi/_gi.x86_64-linux-gnu.so
#7 0x00007f0e6fb84c39 in () at /usr/lib/python2.7/dist-packages/gi/_gi.x86_64-linux-gnu.so
#8 0x00005560917a1f60 in PyEval_EvalFrameEx ()

I have already tried to restart it and it got stuck like this again the next backup cycle.