Amazon S3 storage location missing from Deja Dup 36.1-0ubuntu1

[J. Snow]

I am currently testing out Ubuntu 17.10 and I noticed that Deja Dup (version 36.1-0ubuntu1) no longer supports S3 backups. I have already installed the packages python-boto python-cloudfiles but the "Amazon S3" option is missing from the Storage location tab.

Using dconfig editor, I can see the S3 records created under /org/gnome/deja-dup/s3. The same installation works fine on Ubuntu 16.04. Any thoughts?

lsb_release -d
Description: Ubuntu Artful Aardvark (development branch)

dpkg-query -W deja-dup duplicity
deja-dup 36.1-0ubuntu1
duplicity

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 'remote'
org.gnome.DejaDup last-run ''
org.gnome.DejaDup nag-check ''
org.gnome.DejaDup prompt-check '2017-10-01T10:29:53.542958Z'
org.gnome.DejaDup root-prompt true
org.gnome.DejaDup include-list ['$HOME']
org.gnome.DejaDup exclude-list ['$TRASH', '$DOWNLOAD']
org.gnome.DejaDup last-backup ''
org.gnome.DejaDup allow-metered false
org.gnome.DejaDup delete-after 0
org.gnome.DejaDup.Rackspace username ''
org.gnome.DejaDup.Rackspace container 'ubuntu'
org.gnome.DejaDup.S3 id ''
org.gnome.DejaDup.S3 bucket ''
org.gnome.DejaDup.S3 folder 'ubuntu'
org.gnome.DejaDup.OpenStack authurl ''
org.gnome.DejaDup.OpenStack tenant ''
org.gnome.DejaDup.OpenStack username ''
org.gnome.DejaDup.OpenStack container 'ubuntu'
org.gnome.DejaDup.GCS id ''
org.gnome.DejaDup.GCS bucket ''
org.gnome.DejaDup.GCS folder 'ubuntu'
org.gnome.DejaDup.Local folder 'ubuntu'
org.gnome.DejaDup.Remote uri ''
org.gnome.DejaDup.Remote folder 'ubuntu'
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 'ubuntu'
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 []

[Michael Terry (mterry)]

I assume your testing was on a fresh system, not an upgrade?

We have intentionally hidden several cloud providers by default. See this wiki page for the explanation and how to unhide them:
https://wiki.gnome.org/Apps/DejaDup/Clouds

But on upgrades, your old settings shouldn’t be affected. If that’s the case, this is a new bug. Otherwise, I’ll mark this bug closed as intentional behavior.

(You also shouldn’t have to manually install python-boto and such anymore. If you have S3 set up in deja-dup, we’ll prompt you to install what we need now.)

[J. Snow (jon.snow)]

Thanks Michael, you are right. I was not aware it was hidden. I followed the instructions on the wiki and I activated.

I hope the team will revise the decision for hiding them in the first place. This can be quite confusing for the users.

At any case, thanks a lot for the help.

[bing (ubing)]

+1

*Please* preserve choice for the user, and make the full selection of backend choices visible.

UI design can direct casual users to the friendly backends while preserving convenient choices for experienced users who often have specific needs. Options that are unnecessarily limited on the proprietary OSes is exactly what has driven many users to Linux!

Thanks for the very useful info, and the excellent package.

[Christopher Snowhill (kode54)]

I wouldn’t exactly consider Google Drive “friendly”, but I guess most users don’t have 10+TB of data stored on premises. That much runs for a minimum of $99/mo on Google One.