Deja calls the duplicity command. Monitors the progress and checks that it
finishes. Try getting the underlying command and manually calling
duplicity. When I last looked at this bug duplicity was performing the
backup job to completion. Backups we're ok. Just this error coming from
deja. After looking at the vala code it looked like a vala async call was
failing.
*Check your backups. Do they work?
*Try the deja debug mode to get logs.
export DEJA_DUP_DEBUG=1
deja-dup --backup > dump
Maybe this helps
On Mar 1, 2018 1:19 PM, "Marcin Owsiany" <email address hidden> wrote:
I'm wondering whether something like wrapping the Path.build_filename
call located in libdeja/OperationVerify.vala:connect_to_job in a
realpath() would be enough to fix this issue.
Unfortunately I don't know vala well enough to test this idea.
Title:
'metadata' file not found when creating backup ("Could not restore
‘/home/user /.cache/deja-dup/metadata’: File not found in backup"
Status in Déjà Dup:
Confirmed
Status in duplicity package in Ubuntu:
Incomplete
Bug description:
Linux release: Ubuntu 13.04 64bit
Kernel: 3.8.0-29-generic
Python: 2.7.4
Deja Dup: 26.0
Duplicity: 0.6.21
Hi. I've tried to do my monthly or so backup recently, but Deja Dup
crashed after trying to backup a very large file (VM disk with Windows
7, 50GB or so). I tried to do another one, this time excluding all my
large VM's. However, now when trying to do a backup I'm getting the
following error a few seconds after inputting my encryption password:
Could not restore ‘/home/tom/.cache/deja-dup/metadata’: File not found
in backup
I've tried reinstalling both deja-dup and duplicity, purging
duplicity, deleting deja-dup and duplicity from /home/tom/.cache,
deleting the backup files on the external drive, deleting it's config
as described here http://askubuntu.com/questions/53980/how-to-delete-
all-the-settings-for-deja-dup. I know (well, I have some evidence
supporting this) that the drive itself isn't faulty as I managed to
backup my old laptop to the drive using duplicity and it worked fine
(Fedora 19, deja dup 26.0 I think). I will upload the appropriate logs
momentarily.
Deja calls the duplicity command. Monitors the progress and checks that it
finishes. Try getting the underlying command and manually calling
duplicity. When I last looked at this bug duplicity was performing the
backup job to completion. Backups we're ok. Just this error coming from
deja. After looking at the vala code it looked like a vala async call was
failing.
*Check your backups. Do they work?
*Try the deja debug mode to get logs.
export DEJA_DUP_DEBUG=1
deja-dup --backup > dump
Maybe this helps
On Mar 1, 2018 1:19 PM, "Marcin Owsiany" <email address hidden> wrote:
I'm wondering whether something like wrapping the Path.build_filename OperationVerify .vala:connect_ to_job in a
call located in libdeja/
realpath() would be enough to fix this issue.
Unfortunately I don't know vala well enough to test this idea.
-- /bugs.launchpad .net/bugs/ 1217959
You received this bug notification because you are subscribed to the bug
report.
https:/
Title: deja-dup/ metadata’ : File not found in backup"
'metadata' file not found when creating backup ("Could not restore
‘/home/user /.cache/
Status in Déjà Dup:
Confirmed
Status in duplicity package in Ubuntu:
Incomplete
Bug description:
Linux release: Ubuntu 13.04 64bit
Kernel: 3.8.0-29-generic
Python: 2.7.4
Deja Dup: 26.0
Duplicity: 0.6.21
Hi. I've tried to do my monthly or so backup recently, but Deja Dup
crashed after trying to backup a very large file (VM disk with Windows
7, 50GB or so). I tried to do another one, this time excluding all my
large VM's. However, now when trying to do a backup I'm getting the
following error a few seconds after inputting my encryption password:
Could not restore ‘/home/ tom/.cache/ deja-dup/ metadata’ : File not found
in backup
I've tried reinstalling both deja-dup and duplicity, purging askubuntu. com/questions/ 53980/how- to-delete- settings- for-deja- dup. I know (well, I have some evidence
duplicity, deleting deja-dup and duplicity from /home/tom/.cache,
deleting the backup files on the external drive, deleting it's config
as described here http://
all-the-
supporting this) that the drive itself isn't faulty as I managed to
backup my old laptop to the drive using duplicity and it worked fine
(Fedora 19, deja dup 26.0 I think). I will upload the appropriate logs
momentarily.
To manage notifications about this bug go to: /bugs.launchpad .net/deja- dup/+bug/ 1217959/ +subscriptions
https:/