deja-dup crashes when auto setting turned off during backup

[Christopher Barrington-Leigh]

Let's say a network backup is in progress, and I want to make sure that one does not also happen tomorrow. So I would naturally go to the deja-dup control panel and turn the "auto" slider to OFF in the schedule tab.

Doing this causes an immediate failure of the backup *in progress* and Deja Dup crashes, with the following report in the GUI window:

Traceback (most recent call last):
  File "/usr/bin/duplicity", line 1532, in <module>
    with_tempdir(main)
  File "/usr/bin/duplicity", line 1526, in with_tempdir
    fn()
  File "/usr/bin/duplicity", line 1380, in main
    do_backup(action)
  File "/usr/bin/duplicity", line 1508, in do_backup
    incremental_backup(sig_chain)
  File "/usr/bin/duplicity", line 662, in incremental_backup
    globals.backend)
  File "/usr/bin/duplicity", line 425, in write_multivol
    at_end = gpg.GPGWriteFile(tarblock_iter, tdp.name,
globals.gpg_profile, globals.volsize)
  File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 336, in
GPGWriteFile
    bytes_to_go = data_size - get_current_size()
  File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 328, in
get_current_size
    return os.stat(filename).st_size
OSError: [Errno 2] No such file or directory:
'/home/meuser/.cache/deja-dup/tmp/duplicity-UZ4QXC-tempdir/mktemp-IKK_2v-369'

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: deja-dup 34.2-0ubuntu3.1
ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
Uname: Linux 4.8.0-37-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Feb 14 20:54:19 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-02-12 (368 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: deja-dup
UpgradeStatus: Upgraded to yakkety on 2017-01-21 (24 days ago)

[Vej (vej)]

Hello Christopher.

This looks strange to me (the code for that slider is really simple). So we need to examine this further.

Can you please try if you can reproduce this on your machine using a local backup and a backup to an external harddrive? This might help the developers to find the problematic code.

Another helpfull thing would be the file /tmp/deja-dup.log after performing the following steps:

1. Start your affected network backup using the command "DEJA_DUP_DEBUG=1 deja-dup --backup | tail -n 1000 > /tmp/deja-dup.log" from a terminal
2. Interrupt your backup by changing the value of the slider.
3. Scrub any incriminating file- and usernames from /tmp/deja-dup.log, before uploading.

Best Regards

Vej

[Launchpad Janitor (janitor)]

[Expired for deja-dup (Ubuntu) because there has been no activity for 60 days.]