Deja-Dup and duplicity seemed to work with kernel 4.13.0-19. After that (21 and 22) the issue reappeared.
Very frustrating.
Workaround: Start Deja-Dup manually after it failed.
Careful: Deja-dup claims that the backup has been carried out even when the above error occurs. In my case, there is no backup on the server (so, no, it did not back up, it might have collected the files).
Deja-Dup and duplicity seemed to work with kernel 4.13.0-19. After that (21 and 22) the issue reappeared.
Very frustrating.
Workaround: Start Deja-Dup manually after it failed.
Careful: Deja-dup claims that the backup has been carried out even when the above error occurs. In my case, there is no backup on the server (so, no, it did not back up, it might have collected the files).
Merry Christmas