Duplicity/deja-dup will not create a backup

Bug #1818289 reported by John Bell on 2019-03-01
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Déjà Dup
Undecided
Unassigned

Bug Description

I get the following message:

Error processing remote manifest (duplicity-inc.20190214T141809Z.to.20190221T175834Z.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 =====

Sometimes I get an alternate error message:

Error creating directory /media/john/8126ba33-ddc9-401d-8ee0-0b59a0bada53: Permission denied

(address of my internal disk is correct)

Problem started last week when I tried to deal with multiple keyring requests that I tried to cull, but must have gotten rid of one too many. Or it is something different.

I am on Ubuntu 18.04.2 LTS

deja-dup 37.1-2fakesync1ubuntu0.1
duplicity 0.7.17-0ubuntu1.1

org.gnome.DejaDup last-restore '2019-02-05T06:46:10.011815Z'
org.gnome.DejaDup periodic true
org.gnome.DejaDup periodic-period 7
org.gnome.DejaDup full-backup-period 90
org.gnome.DejaDup backend 'local'

Error processing remote manifest (duplicity-inc.20190214T141809Z.to.20190221T175834Z.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 =====
org.gnome.DejaDup last-run '2019-02-21T18:17:28.744944Z'
org.gnome.DejaDup nag-check '2019-02-07T14:18:30.009530Z'
org.gnome.DejaDup prompt-check '2019-02-05T02:56:12.635538Z'
org.gnome.DejaDup root-prompt true
org.gnome.DejaDup include-list ['$HOME']
org.gnome.DejaDup exclude-list ['$TRASH', '$DOWNLOAD']
org.gnome.DejaDup last-backup '2019-02-21T18:17:28.744944Z'
org.gnome.DejaDup allow-metered false
org.gnome.DejaDup delete-after 0
org.gnome.DejaDup.Rackspace username ''
org.gnome.DejaDup.Rackspace container 'john-ThinkCentre-M910t'
org.gnome.DejaDup.S3 id ''
org.gnome.DejaDup.S3 bucket ''
org.gnome.DejaDup.S3 folder 'john-ThinkCentre-M910t'
org.gnome.DejaDup.OpenStack authurl ''
org.gnome.DejaDup.OpenStack tenant ''
org.gnome.DejaDup.OpenStack username ''
org.gnome.DejaDup.OpenStack container 'john-ThinkCentre-M910t'
org.gnome.DejaDup.GCS id ''
org.gnome.DejaDup.GCS bucket ''
org.gnome.DejaDup.GCS folder 'john-ThinkCentre-M910t'
org.gnome.DejaDup.Local folder '/media/john/8126ba33-ddc9-401d-8ee0-0b59a0bada53/Backups'
org.gnome.DejaDup.Remote uri ''
org.gnome.DejaDup.Remote folder 'john-ThinkCentre-M910t'
org.gnome.DejaDup.Drive uuid ''
org.gnome.DejaDup.Drive icon ''
org.gnome.DejaDup.Drive folder '$HOSTNAME'
org.gnome.DejaDup.Drive name ''
org.gnome.DejaDup.GOA id ''
org.gnome.DejaDup.GOA folder 'john-ThinkCentre-M910t'
org.gnome.DejaDup.GOA type 'google'
org.gnome.DejaDup.File short-name ''
org.gnome.DejaDup.File type 'normal'
org.gnome.DejaDup.File migrated true
org.gnome.DejaDup.File name ''
org.gnome.DejaDup.File path ''
org.gnome.DejaDup.File uuid ''
org.gnome.DejaDup.File icon ''
org.gnome.DejaDup.File relpath @ay []

Michael Terry (mterry) wrote :

Hello! Sorry for slow response.

1) the error message from duplicity indicates a bad encryption password.

2) The settings you posited are confusing. The settings indicate that you are backing up to a local folder. But your error messages indicate that you’re backing up to a pluggable drrive. Which is the reality?

Thanks Michael,

I am backing up to a separate 1 TB SATA drive in my desktop tower
directly plugged to the motherboard.  I think that makes it a local
folder?  This drive has a folder 'Backups' originally created by
Deja-Dup/Duplicity when under Ubuntu 16.04 and I select that as the
location for my backups.  If I just call out the drive and not the
folder Deja-Dup/Duplicity will try to make a full backup on the drive
outside that folder and runs out of room as it ignores the previous backups.

The rest of this may be over-kill, but for completeness this is what I have:

The drive being backed up where the OS and Home folder reside is a
separate SATA

This computer also has a solid state 128 GB drive with Windows which I
do not back up.

History:  I upgraded from Ubuntu 16.04 to 18.04 some months ago and ran
into a load of problems mainly from programs that no longer ran but I
managed to resurrect over time.  Wine became, and remains, a real
problem and some of my old Windows programs became unusable including a
PaperPort/Nuance program essential to read some old ScanSoft data which
is serious to me because I neglected to convert their oddball files to
pdf while I could under Ubuntu 16.04.  But that is not relevant. *I
ended up backing up and reinstalling Ubuntu 18.04 completely ending up
with odd partitioning which I think is limiting my ability to handle
large files - a separate issue I need help on maybe as a separate
submission.*

Thanks again, Michael.

John Bell

On 3/4/19 10:04 PM, Michael Terry wrote:

> Hello! Sorry for slow response.
>
> 1) the error message from duplicity indicates a bad encryption password.
>
> 2) The settings you posited are confusing. The settings indicate that
> you are backing up to a local folder. But your error messages indicate
> that you’re backing up to a pluggable drrive. Which is the reality?
>

John Bell (jkabell) wrote :

Michael,

How do I correct a bad encryption password?  There are only two
possibilities I would have used but I don't see where I could enter it.
I was asked for a keyring once when starting my backup and maybe I used
the wrong one then, but it has never asked me again.

Is there something wrong in my selection of 'local folder' for a
separate SATA drive on my computer?  I am sure that is the way I have
always designated it.

It will be coming up for two weeks without being able to back up, any
help would be appreciated.

John Bell

On 3/4/19 10:04 PM, Michael Terry wrote:
> Hello! Sorry for slow response.
>
> 1) the error message from duplicity indicates a bad encryption password.
>
> 2) The settings you posited are confusing. The settings indicate that
> you are backing up to a local folder. But your error messages indicate
> that you’re backing up to a pluggable drrive. Which is the reality?
>

Michael Terry (mterry) wrote :

Hello, sorry for slow response.

Selecting 'local folder' should be fine. That seems appropriate for your case.

The permission error you're getting is odd. Is the drive sometimes mounted differently?

To clear out any saved password, open the "Passwords and Keys" app and look for the saved "Backup encryption password". Delete that and re-run your backup. It should prompt for the password.

If for some reason, that still doesn't work, the worst case scenario is to back up to a new folder. This will create a new backup series and you can set a new password.

(I'm sorry you're having these problems! Let me know if any of these attempts help.)

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers