Automatic Backup after fresh install of trusty fails: no such file or directory

[David Ayers]

While testing da daily snapshot to verfy a different issue I configured deja-dup to add the typical load to my system.

I configured an SSH upload.

deja-dup failed with:
Traceback (most recent call last):
  File "/usr/bin/duplicity", line 1473, in <module>
    with_tempdir(main)
  File "/usr/bin/duplicity", line 1466, in with_tempdir
    fn()
  File "/usr/bin/duplicity", line 1436, in main
    full_backup(col_stats)
  File "/usr/bin/duplicity", line 541, in full_backup
    globals.backend)
  File "/usr/bin/duplicity", line 402, in write_multivol
    globals.gpg_profile, globals.volsize)
  File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 324, in GPGWriteFile
    file = GPGFile(True, path.Path(filename), profile)
  File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 105, in __init__
    self.logger_fp = tempfile.TemporaryFile( dir=tempdir.default().dir() )
  File "/usr/lib/python2.7/tempfile.py", line 493, in TemporaryFile
    (fd, name) = _mkstemp_inner(dir, prefix, suffix, flags)
  File "/usr/lib/python2.7/tempfile.py", line 239, in _mkstemp_inner
    fd = _os.open(file, flags, 0600)
OSError: [Errno 2] No such file or directory: '/tmp/duplicity-dH5tyj-tempdir/tmpTVOITr'

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: deja-dup 29.1-0ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-1.16-generic 3.13.0-rc7
Uname: Linux 3.13.0-1-generic x86_64
ApportVersion: 2.12.7-0ubuntu6
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Jan 9 21:36:37 2014
InstallationDate: Installed on 2014-01-09 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140109)
SourcePackage: deja-dup
UpgradeStatus: No upgrade log present (probably fresh install)

[David Ayers (ayers)]

While again using deja-dup to produce load for testing another issue, I was able to start a backup manually and it ran for quite some time before crashing with a comparable stack trace.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.