Backing up to ftp or sftp, creates "sftp:" or "ftp:" folder in Deja-Dup launch place
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Déjà Dup |
Expired
|
Undecided
|
Unassigned | ||
deja-dup (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
1. I'm using up to date ArchLinux, x86_64.
2. 20.2-2
3. org.gnome.DejaDup backend 'file'
org.gnome.DejaDup delete-after 0
org.gnome.DejaDup exclude-list ['$TRASH', '$DOWNLOAD', '/home/
org.gnome.DejaDup include-list ['$HOME']
org.gnome.DejaDup last-backup '2011-12-
org.gnome.DejaDup last-restore ''
org.gnome.DejaDup last-run '2011-12-
org.gnome.DejaDup periodic true
org.gnome.DejaDup periodic-period 7
org.gnome.DejaDup prompt-check ''
org.gnome.DejaDup root-prompt true
org.gnome.DejaDup welcomed true
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.
******
Let's say I launch Deja-Dup in home directory /home/ernestas. Then it creates /home/ernestas/sftp:/ or /home/ernestas/ftp:/ directories at which it places backups.
What dependencies is Deja-Dup missing and why isn't it displaying any errors about that?
Out of curiousity, what desktop environment are you using? I've had a similar report (bug 817825) by someone using Deja Dup in KDE. I'm not sure why it would matter, but it may be a clue as to what's going wrong.