Backup Failed: gpg: decrypt_message failed: Unknown system error
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Duplicity |
Invalid
|
Medium
|
Unassigned | ||
Déjà Dup |
Invalid
|
High
|
Unassigned |
Bug Description
After upgrading to 17.10, an error window keeps showing during backup:
GPGError: GPG Failed, see log below:
===== Begin GnuPG log =====
gpg: WARNING: "--no-use-agent" is an obsolete option - it has no effect
gpg: decrypt_message failed: Unknown system error
===== End GnuPG log =====
deja-dup:
Installed: 36.2-0ubuntu1
Candidate: 36.2-0ubuntu1
Version table:
*** 36.2-0ubuntu1 500
500 http://
100 /var/lib/
Mark Stosberg (markstos) wrote : | #1 |
Mark Stosberg (markstos) wrote : | #2 |
When I try "deja-dup --backup" on the command line, I get a message that it is a "creating a fresh backup to protect against backup corruption. This will take longer than normal".
I ran the process with `strace`, saved the output to a logfile, and waited several hours for the crash to happen again. Then I went to review the 29G file that had been generated.
Ignoring the flood of polling related entries, I focused on noting the last files that were accessed before the process crashed. Here are those last related lines of the `strace` output:
```
statfs(
524, f_bavail=6949148, f_files=12763136, f_ffree=11482383, f_fsid=
ze=4096, f_flags=
openat(AT_FDCWD, "/home/
fstat(16, {st_mode=
mmap(NULL, 337916, PROT_READ, MAP_SHARED, 16, 0) = 0x7fec716eb000
statfs(
524, f_bavail=6949148, f_files=12763136, f_ffree=11482383, f_fsid=
ze=4096, f_flags=
openat(AT_FDCWD, "/home/
fstat(18, {st_mode=
mmap(NULL, 32768, PROT_READ, MAP_SHARED, 18, 0) = 0x7fec80007000
eventfd2(0, EFD_CLOEXEC|
write(6, "\1\0\0\0\0\0\0\0", 8) = 8
futex(0x55972ec
futex(0x55972ec
futex(0x55972ec
read(20, "\1\0\0\0\0\0\0\0", 16) = 8
write(20, "\1\0\0\0\0\0\0\0", 8) = 8
futex(0x55972f0
close(20) = 0
unlink(
rmdir("
lstat("
lstat("
lstat("/home/mark", {st_mode=
lstat("/home", {st_mode=
lstat("/", {st_mode=
```
So it looks like the GVFS metadata file was the last one to be accessed. I presume the `unlink` and `rmdir` calls are part of a clean-up at the end and happened after the error.
Now I need to shop for a new backup solution!
Rusty Abbott (rustyabbott) wrote : | #3 |
Matthew & Mark,
Did either of you find a solution to this? I had the same problem with 17.10. I've recently updated to 18.04 and still getting the same error message:
GPGError: GPG Failed, see log below:
===== Begin GnuPG log =====
gpg: WARNING: "--no-use-agent" is an obsolete option - it has no effect
gpg: decrypt_message failed: Unknown system error
===== End GnuPG log =====
-Rusty
Mathieu Leplatre (mathieu.leplatre) wrote : | #4 |
Sorry, I didn't.
I'm using Restic meanwhile... it works well, but I would really prefer Deja Dup since it was well integrated into the desktop
Hello everyone.
Thanks for reporting this bug. Can you please add the following informations, so the developers can figure out what exactly went wrong:
1. The distribution of Linux you're using:
lsb_release -d
2. The version of deja-dup and duplicity:
(if on Ubuntu or Debian:)
dpkg-query -W deja-dup duplicity
(if on Fedora or other RPM-based systems:)
rpm -q deja-dup duplicity
3. The file /tmp/deja-
gsettings list-recursively org.gnome.DejaDup > /tmp/deja-
4. The file /tmp/deja-dup.log after running the appropriate line below and replicating the problem (you may want to scrub the log of any incriminating file names or details):
* If you're having problems backing up:
DEJA_
* If you're having problems restoring:
DEJA_
Changed in deja-dup: | |
status: | New → Confirmed |
status: | Confirmed → Incomplete |
Launchpad Janitor (janitor) wrote : | #6 |
[Expired for Déjà Dup because there has been no activity for 60 days.]
Changed in deja-dup: | |
status: | Incomplete → Expired |
Alessander Botti Benevides (alessanderbotti) wrote : | #7 |
- deja-dup.gsettings Edit (1.9 KiB, text/plain)
1. Description: Ubuntu 18.04.1 LTS
2. deja-dup 37.1-2fakesync1
duplicity 0.7.17-0ubuntu1
3. attached
Alessander Botti Benevides (alessanderbotti) wrote : | #8 |
Changed in deja-dup: | |
status: | Expired → Confirmed |
Chris (fesoft) wrote : | #9 |
Same here on 18.04 - deleting the backupo and starting over did not help as well.
Mortimer (blackpenguin) wrote : | #10 |
I had the same problem after upgrading from 16.04 to 18.04.
1) Ubuntu 18.04.1 LTS
2)
deja-dup 37.1-2fakesync1
duplicity 0.7.17-0ubuntu1
--error message below--
Backup Failed
Error processing remote manifest (duplicity-
===== Begin GnuPG log =====
gpg: WARNING: "--no-use-agent" is an obsolete option - it has no effect
gpg: AES encrypted data
gpg: encrypted with 1 passphrase
gpg: decryption failed: Bad session key
===== End GnuPG log =====
Steven Palmer (celtaweb) wrote : | #11 |
I also had the same problem after upgrading from 16.04 to 18.04.
-- system below --
Ubuntu 18.04.2 LTS
deja-dup 37.0
duplicity 0.7.17
-- error message below --
GPGError: GPG Failed, see log below:
===== Begin GnuPG log =====
gpg: WARNING: "--no-use-agent" is an obsolete option - it has no effect
gpg: decrypt_message failed: Unknown system error
===== End GnuPG log =====
Laurenz (lalten) wrote : | #12 |
I have the same problem. I don't remember updating anything special, my backups just started to fail last week with the error message
Error processing remote manifest (duplicity-
===== Begin GnuPG log =====
gpg: WARNING: "--no-use-agent" is an obsolete option - it has no effect
gpg: decrypt_message failed: Unknown system error
===== End GnuPG log =====
I tried to update all versions, but the error remains.
Ubuntu 18.04.2 LTS
deja-dup 39.1 (git 69b360b8)
duplicity 0.7.18.2 (ppa:duplicity-
gpg (GnuPG) 2.2.4 (https:/
Laurenz (lalten) wrote : | #13 |
I found my problem using
DEJA_DUP_DEBUG=1 deja-dup --backup
excerpt:
DUPLICITY: WARNING 1
DUPLICITY: . Attempt 1 failed. GSResponseError: GSResponseError: 403 Forbidden
DUPLICITY: . <?xml version='1.0' encoding=
DUPLICITY: ERROR 1
DUPLICITY: . Error processing remote manifest (duplicity-
DUPLICITY: . ===== Begin GnuPG log =====
DUPLICITY: . gpg: WARNING: "--no-use-agent" is an obsolete option - it has no effect
DUPLICITY: . gpg: decrypt_message failed: Unknown system error
DUPLICITY: . ===== End GnuPG log =====
DUPLICITY: .
I guess it would be very helpful if deja-dup would propagate this warning to the user.
Michael Terry (mterry) wrote : | #14 |
Mortimer, from comment 10: your problem is a recently fixed passphrase bug. See https:/
I’d like to keep this bug focused on the “unknown system error” bug.
Unfortunately, I’m not sure how to proceed on that yet. If anyone knows how to reproduce it, please let me know.
I’ll add duplicity as an affected project, in case they’ve seen this error before.
Mortimer (blackpenguin) wrote : | #15 |
Michael,
(re: comment 10, 14)
Thank you. It looks like that machine began backing up again, maybe 7 days ago. I have installed updates as they came up but did not make any modifications to try to address the issue.
That machine was using full disk encryption which may explain the different error message.
I added the "unknown system error" to the title to emphasize that this is not about ever GPG-bug, but about this issue (see comment #14).
summary: |
- Backup Failed: gpg: decrypt_message failed + Backup Failed: gpg: decrypt_message failed: Unknown system error |
Changed in deja-dup: | |
importance: | Undecided → High |
Phil Ayres (ayres-phil) wrote : | #17 |
This error appears for me too when the periodic secret validation occurs. The validation takes a long time and eventually times out.
Ubuntu 18.04.2 LTS
deja-dup 37.1-2fakesync1
duplicity 0.7.17-0ubuntu1.1
gpg (GnuPG) 2.2.4
Running `gpg --no-use-agent` on the command line returns
gpg: WARNING: "--no-use-agent" is an obsolete option - it has no effect
Presumably this is due to
https:/
Line 91: argv.append(
OK, so the agent is always required with gpg 2.1+. So either it looks like deja shouldn't be passing the option, or should offer a way to specify the gpg version.
Since it takes ages to time out after I have entered the secret for validation, I'm guessing that it is more than a warning here, and that gpg is blocking the request.
A long way of say this is affecting me too.
Vadim Zeitlin (vz-ubuntu) wrote : | #18 |
Just another failure report with Duplicity 0.7.18.2 included in Debian Buster:
# PASSPHRASE='xxx' /usr/bin/duplicity -v 6 --archive-dir /nobackup/
Using archive dir: /nobackup/
Using backup name: mail
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
ssh: Connected (version 2.0, client OpenSSH_7.6)
/usr/lib/
m.add_
/usr/lib/
self.curve, Q_S_bytes
/usr/lib/
hm.add_
/usr/lib/
operation
/usr/lib/
Changed in duplicity: | |
status: | New → Confirmed |
Same problem since a week or so on
- Ubuntu 20.04.1 LTS
- 20.04.1 LTS
Kenneth Loafman (kenneth-loafman) wrote : Update bug #1728548, status confirmed, importance medium | #20 |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
status confirmed
importance medium
done
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiE
M/GuUwgArql80v8
zcEwcReF5KWl4ud
bgQi9Kdri42xf+
O3zxnZyshlxFf/
UXKHZYdpcRGjw+
kHSFVbfr4rTqKiZ
=gTQM
-----END PGP SIGNATURE-----
Changed in duplicity: | |
importance: | Undecided → Medium |
Thomas Hamilton Lipscomb (hari-seldon) wrote (last edit ): | #21 |
- deja-dup.log Edit (43.2 KiB, text/plain)
QUESTION: How do I delete the corrupted Deja Dup backup to fix this bug? Which files do I delete? I see 3 folders in my backup drive:
$RECYCLE.BIN
System Volume Information
thomas-G752VL (my backup folder)
What about deleting ~/.cache/deja-dup/
I also have this bug. I think it happened when my laptop froze and I forced a shutdown. Even though I think Deja Dup was not backing up at the time that may have corrupted the backup.
GPGError: GPG Failed, see log below:
===== Begin GnuPG log =====
gpg: no valid OpenPGP data found.
gpg: decrypt_message failed: Unknown system error
===== End GnuPG log =====
1. The distribution of Linux you're using:
Ubuntu 20.04.3 LTS
2. The version of deja-dup and duplicity:
deja-dup 40.7-0ubuntu1
duplicity 0.8.11.1612-1
3. The file /tmp/deja-
org.gnome.DejaDup exclude-list ['$TRASH', '$DOWNLOAD']
org.gnome.DejaDup allow-metered false
org.gnome.DejaDup root-prompt true
org.gnome.DejaDup periodic-period 1
org.gnome.DejaDup include-list ['/home/thomas', '/mnt/M2DATA/
org.gnome.DejaDup prompt-check '2020-11-
org.gnome.DejaDup periodic true
org.gnome.DejaDup delete-after 0
org.gnome.DejaDup last-restore ''
org.gnome.DejaDup last-run '2021-10-
org.gnome.DejaDup full-backup-period 90
org.gnome.DejaDup last-backup '2021-10-
org.gnome.DejaDup backend 'drive'
org.gnome.DejaDup nag-check '2021-08-
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
4. The file /tmp/deja-dup.log after running the appropriate line below and replicating the problem (you may want to scrub the log of any incriminating file names or details):
* If you're having problems backing up:
DEJA_
Kenneth Loafman (kenneth-loafman) wrote : | #22 |
OK, from the description and the error message 'Unknown system error' I'm sure a backup file in the backup set is corrupted. There are dozens of reasons for file corruption not having to do with software malfunction. We need reproducible scenarios to find the malfunction if it's software.
To work around it, remove the last full or incremental backup from local cache and remote store. First find the manifest file, i.e. duplicity-
$ rm <local-
$ <cli-tool-
This will clean out the bad backup.
WARNING: on incremental backups make sure you do not remove a backup in the middle of the chain or you will break the chain and recovery will be impossible.
Thomas Hamilton Lipscomb (hari-seldon) wrote (last edit ): | #23 |
- Screenshot from 2021-12-18 05-39-28.png Edit (693.7 KiB, image/png)
I deleted both the cache and the backup on my external SSD and that didn't fix it. Every time I tried one of the below I deleted those and made a fresh one. Attached is the screenshot showing the error.
I used the code below to trim all of my filenames in Desktop, Documents, Downloads, Music, Pictures, and Videos to be no more than 100 characters long, just in case filenames being too long was the issue. That didn't fix it.
export n=100
find . -type f \
! -name '.*' \
-regextype egrep \
! -regex '.*\.[^
-regex '.*[^/]
-execdir bash -c '
for f in "${@#./}"; do
mv -- "$f" "${f:0:
done' bash {} +
I manually (not using Deja Dup) copied my files from my ext4 Linux filesystem to an NTFS external backup drive to check to make sure no filename has illegal characters like | because for example if the filename has | in it then a warning message pops up and says you can't copy that file to an NTFS file system do you want to skip it. I removed the illegal characters and now it copies to NTFS without any warnings but the backup still fails so that wasn't it.
I reformatted my Deja Dup backup drive Samsung_T5 from exFAT to ext4 just in case Deja Dup doesn’t like exFAT (cross-platform Solid State Drive filesystem) and likes ext4 (Linux filesystem) better. That didn't fix it.
I uninstalled Deja Dup using "sudo apt-get purge deja-dup" then reinstalled it from the Ubuntu Snap store. I also tried unencrypted backup using Deja Dup instead of encrypted. Doing both of those didn't fix it. Attached is the "Restore Failed: Failed with an unknown error." screenshot of my Ubuntu.
I cannot find /tmp/deja-
At this point my computer repair guy recommended trying Bacula (https:/
Changed in duplicity: | |
status: | Confirmed → Invalid |
Michael Terry (mterry) wrote : | #24 |
Cleaning up old tickets
Changed in deja-dup: | |
status: | Confirmed → Invalid |
This happened to me as well.
When I went to check the remote site where the backups were stored, I found they hadn't been running for some time.
So I'm not sure whether in my case:
* The backups were already failing, but now the error is starting to be surfaced
* The backups are actually starting to work now, but the delta since the last backup is so large, that this triggers a failure
* There is a new bug that is unrelated to why my backups weren't working before.
At this point I'll probably try to just start over or use a different backup system-- clearly deja-dup / duplicity isn't performing the basic functionality for me and hasn't for some time.