Comment 32 for bug 1855736

It is indeed strange, because I can't reproduce it now either. I get the errors in #30 instead, with deja-dup saying it can't understand the duplicity version.

I think what may have happened is that because I couldn't get deja-dup to work I used the duplicity command line, and encrypted this particular backup. I don't normally encrypt this backup (which is mainly system files, config files etc). Is 'decode' something to do with encryption?

Once duplicity seemed to be sorted I redid the backup without encryption, and now I get the issues in #30.