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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727653 Title: error: can't start new thread To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1727653/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
