On what target are you backing up? Is it an sftp server as in #4?
Also add the following informations please, so the developers know what this is about:
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-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
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_DUP_DEBUG=1 deja-dup --backup | tail -n 1000 > /tmp/deja-dup.log
The first one providing this information can set the status to "Confirmed".
Hello Marek, mikeyphi and Lawrence!
On what target are you backing up? Is it an sftp server as in #4?
Also add the following informations please, so the developers know what this is about:
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- dup.gsettings after running the following line (you may want to scrub the file of any incriminating file names or details): dup.gsettings
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: DUP_DEBUG= 1 deja-dup --backup | tail -n 1000 > /tmp/deja-dup.log
DEJA_
The first one providing this information can set the status to "Confirmed".
Thanks
Vej