Description of problem: Under Fedora 15, when deja-dup completed it presented a dialog telling me it had been successful. Now that I am on FC17, deja-dup appears to run OK, but eventually the application just goes away. There is no indication of completion, but abrt does not report a crash. How can I tell if the process has completed OK? Version-Release number of selected component (if applicable): deja-dup 20. How reproducible: Run a backup and wait for completion. Steps to Reproduce: 1. Run a backup. Actual results: Application dies without reporting success or failure. Expected results: Success dialog displayed. Additional info: As deja-dup has been my backup solution of choice, I need to know if it is working because, if it is failing, my backups will not be valid.
deja-dup-22.1-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/deja-dup-22.1-1.fc17
Package deja-dup-22.1-1.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing deja-dup-22.1-1.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-6642/deja-dup-22.1-1.fc17 then log in and leave karma (feedback).
Would you mind filing this issue upstream at https://launchpad.net/deja-dup
OK - will do, thanks. "8-)
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.