Drive storage location is not selectable

Bug #1757970 reported by Chris McDonough on 2018-03-22
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Déjà Dup
Undecided
Unassigned

Bug Description

I am having some difficulty convincing deja-dup to put its volume files on an encrypted partition on my hard disk. Via the configuration GUI, I have these options selectable:

Google
NextCloud
Network Server
2.0 GB Encrypted
Local Folder

However, I also have a "1.0 GB Encrypted" partition in my system (it's on a different HDD than the 2.0 GB one listed), but I can't convince deja-dup to allow me to select it. It works fine via the Disks app, etc. Because it's encrypted, I want deja-dup to ask me for the decryption key when it starts the backup, so I can't just use "Local Folder" and type the place in where it might be (but probably isnt yet) mounted.

I can probably manually hack it via dconf-editor (the "drive" subconfig indeed shows the info for 2.0 GB Encrypted), but I'd rather figure out what's happening and do it right.

Any clues appreciated.

$ lsb_release -d
Description: Ubuntu Bionic Beaver (development branch)

$ dpkg-query -W deja-dup duplicity
deja-dup 37.1-2fakesync1
duplicity 0.7.17-0ubuntu1

$ gsettings list-recursively org.gnome.DejaDup
org.gnome.DejaDup last-restore ''
org.gnome.DejaDup periodic false
org.gnome.DejaDup periodic-period 7
org.gnome.DejaDup full-backup-period 90
org.gnome.DejaDup backend 'local'
org.gnome.DejaDup last-run '2018-03-21T13:15:08.121034Z'
org.gnome.DejaDup nag-check '2018-03-21T06:24:07.128947Z'
org.gnome.DejaDup prompt-check '2018-03-20T11:29:52.387006Z'
org.gnome.DejaDup root-prompt true
org.gnome.DejaDup include-list ['$HOME']
org.gnome.DejaDup exclude-list ['$TRASH', '$DOWNLOAD']
org.gnome.DejaDup last-backup '2018-03-21T13:15:08.121034Z'
org.gnome.DejaDup allow-metered false
org.gnome.DejaDup delete-after 182
org.gnome.DejaDup.Rackspace username ''
org.gnome.DejaDup.Rackspace container 'thinkm'
org.gnome.DejaDup.S3 id ''
org.gnome.DejaDup.S3 bucket ''
org.gnome.DejaDup.S3 folder 'thinkm'
org.gnome.DejaDup.OpenStack authurl ''
org.gnome.DejaDup.OpenStack tenant ''
org.gnome.DejaDup.OpenStack username ''
org.gnome.DejaDup.OpenStack container 'thinkm'
org.gnome.DejaDup.GCS id ''
org.gnome.DejaDup.GCS bucket ''
org.gnome.DejaDup.GCS folder 'thinkm'
org.gnome.DejaDup.Local folder '/media/chrism/thinkq-backup/deja-dup'
org.gnome.DejaDup.Remote uri ''
org.gnome.DejaDup.Remote folder 'thinkm'
org.gnome.DejaDup.Drive uuid '1e59470e-35bd-4b3a-9252-09fab84d697e'
org.gnome.DejaDup.Drive icon '. GEmblemedIcon .%20GThemedIcon%20drive-harddisk-usb%20drive-harddisk%20drive .%20GEmblem%20changes-prevent%201'
org.gnome.DejaDup.Drive folder 'thinkm'
org.gnome.DejaDup.Drive name '2.0 TB Encrypted'
org.gnome.DejaDup.GOA id ''
org.gnome.DejaDup.GOA folder 'thinkm'
org.gnome.DejaDup.GOA type 'google'
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 []

Providing deja-dup debug log seems inappropriate; i'm neither having problems backing up nor restoring, only selecting the proper storage location.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers