>> You apparently performed a full backup on 2016-11-29 at 01:52 UTC,
>> did everything work fine during this backup? Was it successful ?
> Don't think so
Don't think so either, because your full backup on that date is only one
volume long and that volume is 120 bytes long:
ls -l /home/david/Dr
Thanks for the information. First of all, as reported by the log file
you sent and the listing of your backup directory, there is an
uncompressed backup volume in your volume directory, and an uncompressed
file of files signatures, created or last modified on Dec 22:
duplicity-full.20161129T0152
Nathanael
using Fish
ls -lR ~/.cache/deja-dup
/home/david/.cache/deja-dup:
total 4
drwxrwxr-x 2 david david 4096 Jan 14 12:50 f00ff76508010e2a830dd26b1d39db42/
/home/david/.cache/deja-dup/f00ff76508010e2a830dd26b1d39db42:
total 8
-rw-rw-r-- 1 david david 165 Jan 14 12:50
duplicity-full.2016112
Also, from the content of your log-file, I've got the impression that
there isn't a single well-formed backup chain in your backup directory.
Can you check with:
ls -l /home/david/Dropbox/Backups
--
You received this bug notification because you are a member of Desktop
Packages, which is subsc
You apparently performed a full backup on 2016-11-29 at 01:52 UTC, did
everything work fine during this backup? Was it successful ?
When did you run first into this problem - on the first incremental
backup ?
--
You received this bug notification because you are a member of Desktop
Packages, whi
The "status" Vej refers to is the bug status, on this web page, to
switch from "incomplete" to "new".
Thanks for the log. Can you please show the content of your cache
directory?
ls -lR ~/.cache/deja-dup
--
You received this bug notification because you are a member of Desktop
Packages, which
Nathanael
Tried the commands you gave in fish
and also the ones intended for bash in bash.
some created the log but 3 times out of four the log was blank/empty
Attached is the one that did leave a log.
Notably every time start of backup produced "Backup failed"
sTraceback (most recent call last):
It's because you're using the fish shell instead of the more common bash
shell. If I understand correctly, the fish translation of Vej's command
is:
env DEJA_DUP_DEBUG=1 deja-dup --backup | tail -n 1000 > /tmp/deja-
dup.log
or:
set -x DEJA_DUP_DEBUG 1
deja-dup --backup | tail -n 1000 > /tm
found and attached
Also I got
DEJA_DUP_DEBUG=1 deja-dup --backup | tail -n 1000 > /tmp/deja-dup.log
Unsupported use of '='. To run 'deja-dup' with a modified environment, please
use 'env DEJA_DUP_DEBUG=1 deja-dup…'
david@david-Lenovo-H535 ~>
** Attachment added: "deja-dup.gsettings"
https:
Hello David.
Thanks for the settings. Now we are still missing the /tmp/deja-dup.log
with the output from the second command (that one, which did the run in
debug mode).
Best Regards
Vej
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Sorry
Didn't recognize the commands as such.
Tmp contents:
org.gnome.DejaDup last-restore ''
org.gnome.DejaDup periodic true
org.gnome.DejaDup full-backup-period 90
org.gnome.DejaDup backend 'file'
org.gnome.DejaDup last-run ''
org.gnome.DejaDup nag-check ''
org.gnome.DejaDup prompt-check '2017-01-
Did you executed the two commands before? If so did they failed somehow?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1652410
Title:
duja-dup AssertionError: ({1: 'duplicity-
ful
What I have not done is uninstall, purge & reinstall.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1652410
Title:
duja-dup AssertionError: ({1: 'duplicity-
full.20161129T015237Z.
Hello Vej
my /Tmp contains no file with deja-dup.settings
** Attachment added: "/tmp deja-dup"
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1652410/+attachment/4801706/+files/Screenshot%20from%202017-01-08%2013-45-49.png
--
You received this bug notification because you are a m
Hello David,
can you provide us with the following informations please:
The file /tmp/deja-dup.gsettings after running the following line (you may want
to scrub the file of any incriminating file names or details):
gsettings list-recursively org.gnome.DejaDup > /tmp/deja-dup.gsettings
The f
15 matches
Mail list logo