Comment 81 for bug 1217959

@Xwarman: Please be aware that you disabled one of the major checks to ensure a successful backup.

@all: I am wondering if this happens before or after the backup taking place?

A more recent output of the file /tmp/deja-dup.log after running the appropriate line below and replicating the problem might be helpful as well. Especially because there seems to be another problem in the backup of the original reporter. 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