Comment 103 for bug 1217959

Working at a fresh install of Kubuntu 18.04.1 LTS in February 2019 - at a Lenovo X220, with a i5 processor and a 1 TB Samsung 860 EVO SSD, together with a 4 TB external HD, "WD My Passport". However, I still stumble upon the same bug. However, I seemingly manage to work around it by acting as follows:
TERMINAL >> sudo apt-get purge deja-dup duplicity > sudo apt-get autoremove > sudo reboot now > after the reboot: TERMINAL >> apt-get install deja-dup duplicity > sudo deja-dup.

On one hand, deja-dup has been making a first back-up ever since I hit the "sudo-deja" commando - now, a few hours ago.

On the other hand, I got this terminal feedback in the first minutes after hitting the "sudo deja-dup" commanend.

bas@Viaconsensus-iter:~$ sudo deja-dup

** (org.gnome.DejaDup:2519): CRITICAL **: 14:34:51.229: string_contains: assertion 'self != NULL' failed
gpg: WARNING: unsafe ownership on homedir '/home/bas/.gnupg'

** (org.gnome.DejaDup:2519): WARNING **: 14:35:56.153: AssistantOperation.vala:904: Error calling StartServiceByName for org.freedesktop.secrets: Timeout was reached

After "Timeout was reached", deja-dup seemingly started the backup process that is still ongoing.

I keep you posted here on my experiences.

Yours,
Bas G. ROufs.