"could not back up files" dialog never shown; breaks scheduled backups

Bug #1232873 reported by Siddu
34
This bug affects 6 people
Affects Status Importance Assigned to Milestone
Déjà Dup
Fix Released
Undecided
Unassigned
deja-dup (Arch Linux)
New
Undecided
Unassigned
deja-dup (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

On the conclusion of a backup, if any nonreadable files exist in the backup source directories, Deja Dup shows a notification at the bottom of my screen telling me that the backup completed but not all files were able to be backed up; "see dialog for details". However, this dialog never appears. As a result, the "deja-dup --backup --auto" process never terminates, as it's waiting for me to close a dialog that never appeared in the first place.

This effectively breaks the automatic, "set-and-forget" backup strategy, as deja-dup-monitor will not launch another scheduled backup until the deja-dup process exits, which will never happen.

This only happens when deja-dup is launched with "deja-dup --backup --auto"; launching with "deja-dup --backup" (no auto) does show the dialog at the end of the process, allowing me to close it and properly terminate the backup.

~$ lsb_release -d
Description: Ubuntu Saucy Salamander (development branch)

~$ dpkg-query -W deja-dup duplicity
deja-dup 27.3.1-0ubuntu1
duplicity 0.6.21-0ubuntu4

Revision history for this message
arst06d (david-arstall) wrote :

Yes - also affects me running xubuntu 13:10.

I don't see a dialog - only way I know the backup has failed (or is still waiting to finish) is if I access the Deja-dup ui and the Backup Now button is greyed out. I then check Task Manager and see "deja-dup --backup --auto" is still alive. Kill that and all OK.

I don't know what file(s) it gets hung up on as I don't see a dialog.

This was also raised in Question #237446 but was never resolved as far as I can see.

Changed in deja-dup:
status: New → Confirmed
Revision history for this message
Matthew Haughton (snafu109) wrote :

I have the exact same issue.

$ lsb_release -d
Description: Ubuntu 13.10

$ dpkg-query -W deja-dup duplicity
deja-dup 27.3.1-0ubuntu1
duplicity 0.6.21-0ubuntu4.1

Running XFCE.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in deja-dup (Ubuntu):
status: New → Confirmed
Revision history for this message
palmerito0 (sandiegobutterflies) wrote :

Bump. Affects me on Linux Mint 17.3 Rosa.

Revision history for this message
simon place (psiplace) wrote :

same here. ubuntu mate 15.10

waste of time.

i even had to check system monitor to find out this was called "Déjà Dup" to be able to report this bug, but 3 years down the line still being put in new systems, probably this is just more waste of my time.

Revision history for this message
TheOldFellow (theoldfellow) wrote :

Does anyone know of a backup program that works? This one never terminates and doesn't report errors to alog like any, and I mean ANY, sensible, properly programmed program.

From this raised in 2008, and still unaddressed in 2016, 8 YEARS later, it isn't actually maintained either.

Revision history for this message
Vej (vej) wrote :

Hello everyone affected. Is this still related to an option called "--auto" as described by the original author?

I could not find such an option in a recent version of Déjà Dup.

Changed in deja-dup:
status: Confirmed → Incomplete
Changed in deja-dup (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Michael Terry (mterry) wrote :

--auto is how we launch the background backups.

I think this bug has been fixed in recent releases by a more concerted effort to keep the progress windows on top of the rest of the interface. But if folks can still reproduce using a recent Deja Dup (40+ I’d say), please reopen and I can try to reproduce.

Changed in deja-dup:
status: Incomplete → Fix Released
Changed in deja-dup (Ubuntu):
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.