Comment 43 for bug 1278529

Experiencing the same issue here

F19 x64 deja-dup-26.0-1.fc19.x86_64

Dave Allan's workaround is functional; to findout the correct bucket it's trying to use however run:

DEJA_DUP_DEBUG=1 deja-dup --backup

Pay attention to the

DUPLICITY: . Args: /usr/bin/duplicity collection-status line,

--s3-use-new-style s3+http://deja-dup-auto-XXXXXXXXXXXX/YOUR_FOLDER

DUPLICITY: INFO 1
DUPLICITY: . Backend error detail: Traceback (most recent call last):
DUPLICITY: . File "/usr/bin/duplicity", line 1502, in <module>
DUPLICITY: . with_tempdir(main)
DUPLICITY: . File "/usr/bin/duplicity", line 1496, in with_tempdir
DUPLICITY: . fn()
DUPLICITY: . File "/usr/bin/duplicity", line 1345, in main
DUPLICITY: . do_backup(action)
DUPLICITY: . File "/usr/bin/duplicity", line 1374, in do_backup
DUPLICITY: . sync_archive(decrypt)
DUPLICITY: . File "/usr/bin/duplicity", line 1104, in sync_archive
DUPLICITY: . remlist = globals.backend.list()
DUPLICITY: . File "/usr/lib64/python2.7/site-packages/duplicity/backend.py", line 429, in list
DUPLICITY: . return map(tobytes, self._list())
DUPLICITY: . File "/usr/lib64/python2.7/site-packages/duplicity/backends/_boto_single.py", line 297, in _list
DUPLICITY: . raise BackendException("No connection to backend")
DUPLICITY: . BackendException: No connection to backend
DUPLICITY: .

DUPLICITY: ERROR 23 BackendException
DUPLICITY: . BackendException: No connection to backend

1) The error is miss leading the connection to s3 appears fine; this is instead the absense of a bucket being present (additional checking required).
2) deja _used_ to auto create buckets; but no longer does so (regression?)
3) From the gui you may specify the folder but not the bucket compounding the issue.