Home / ubuntu / Questions / 1057627
In Process
C. Davis
Asked: 2018-07-20 07:40:21 +0800 CST

Duplicity fails with bad session key error

  • 772

This is the error:

Error processing remote manifest (duplicity-inc.20180712T125810Z.to.20180719T130228Z.manifest.gpg): GPG Failed, see log below:
===== Begin GnuPG log =====
gpg: WARNING: "--no-use-agent" is an obsolete option - it has no effect
gpg: AES256 encrypted data
gpg: encrypted with 1 passphrase
gpg: decryption failed: Bad session key
===== End GnuPG log =====
gnupg backup duplicity 18.04

2 Answers

  1. The author of Deja Dup has published https://wiki.gnome.org/Apps/DejaDup/PassphraseProblems2019 in which he describes possible reasons due to bugs in earlier versions of Deja Dup and bugs in the underlying duplicity.

    TL;DR is that you might have entered a wrong password when being prompted. Unfortunately at least earlier versions of duplicity don't check if the passed passphrase equals the one used in past backups.

    In my case the most recent backup files were encrypted with a wrong passphrase. Said document provides a command to check that. Thus, I simply deleted those and ran backup again.

    Ubuntu 18.04 uses Deja Dup version 37.0 which still contains this bug. According to the document linked above, the bug is fixed as of 39.1.

    • 4
    • 3