Comment 2 for bug 1759313

Hello

My answer is bottom:

Best Regards
Tom

W dniu 28.03.2018 o 18:32, Vej pisze:
> Hello!
>
> Sorry for you having problems with Déjà Dup.
> In order to know what exactly is happening when you try to do backup I request the following informations:
>
> 1. The distribution of Linux you're using:
> lsb_release -d
Ubuntu 17.10
>
> 2. The version of deja-dup and duplicity:
> (if on Ubuntu or Debian:)
> dpkg-query -W deja-dup duplicity
deja-dup    36.3-0ubuntu0.1
duplicity    0.7.12-1ubuntu1

>
> (if on Fedora or other RPM-based systems:)
> rpm -q deja-dup duplicity
>
> 3. 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
org.gnome.DejaDup last-restore ''
org.gnome.DejaDup periodic true
org.gnome.DejaDup periodic-period 7
org.gnome.DejaDup full-backup-period 90
org.gnome.DejaDup backend 'local'
org.gnome.DejaDup last-run ''
org.gnome.DejaDup nag-check ''
org.gnome.DejaDup prompt-check 'disabled'
org.gnome.DejaDup root-prompt true
org.gnome.DejaDup include-list ['/home/xx002']
org.gnome.DejaDup exclude-list ['$TRASH', '$DOWNLOAD',
'/home/xx002/Publiczny', '/home/xx002/Pulpit', '/home/xx002/Szablony',
'/home/xx002/Wideo', '/home/xx002/Muzyka', '/home/xx002/Obrazy']
org.gnome.DejaDup last-backup ''
org.gnome.DejaDup allow-metered false
org.gnome.DejaDup delete-after 182
org.gnome.DejaDup.Rackspace username ''
org.gnome.DejaDup.Rackspace container 'xx002-Latitude-E6520'
org.gnome.DejaDup.S3 id ''
org.gnome.DejaDup.S3 bucket ''
org.gnome.DejaDup.S3 folder 'xx002-Latitude-E6520'
org.gnome.DejaDup.OpenStack authurl ''
org.gnome.DejaDup.OpenStack tenant ''
org.gnome.DejaDup.OpenStack username ''
org.gnome.DejaDup.OpenStack container 'xx002-Latitude-E6520'
org.gnome.DejaDup.GCS id ''
org.gnome.DejaDup.GCS bucket ''
org.gnome.DejaDup.GCS folder 'xx002-Latitude-E6520'
org.gnome.DejaDup.Local folder '/mnt/sdb1/KOPIA AUTOMATYCZNA'
org.gnome.DejaDup.Remote uri ''
org.gnome.DejaDup.Remote folder 'xx002-Latitude-E6520'
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 'xx002-Latitude-E6520'
org.gnome.DejaDup.GOA type 'owncloud'
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 []
>
> 4. The file /tmp/deja-dup.log after running the line below and replicating the problem (you may want to scrub the log of any incriminating file names or details):
> DEJA_DUP_DEBUG=1 deja-dup --backup | tail -n 1000 > /tmp/deja-dup.log
I can't find in my all HDD (with fidden files on) any file with

deja-dup.log

name. If Dej-Dup tray make another copy I have error mesage like this on
screanshot.
>
> Best Regards
>
> Vej
>
> ** Changed in: deja-dup
> Status: New => Incomplete
>