Hide Forgot
abrt version: 1.1.14 architecture: x86_64 Attached file: backtrace cmdline: deja-dup component: deja-dup crash_function: deja_dup_operation_start_finish executable: /usr/bin/deja-dup kernel: 2.6.35.10-74.fc14.x86_64 package: deja-dup-16.1-2.fc14 rating: 4 reason: Process /usr/bin/deja-dup was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1294927557 uid: 500 How to reproduce ----- 1. Click 'Back Up...'. 2. Start the backup (i.e. click 'Back Up' again) without a backup drive plugged in. 3. Click cancel on the waiting for connection screen. 4. Plug in the backup drive with deja-dup still running. I'm not sure if this is a consistently reproducible crash.
Created attachment 473325 [details] File: backtrace
Package: deja-dup-16.1-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Cancelled the dialog asking for my Amazon S3 data 2. Crash
I believe that this is fixed in 17.6. Please let me know if you can reproduce with that or later.
Package: deja-dup-16.1-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Start Deja Dup and try to run a backup without the needed volume mounted. 2. Cancel the dialog asking you to mount the volume. 3. Modify prefs to remove one items from the exclude list; close the prefs dialog. 4. With Deja Dup still running but sitting idle at the main entry window, plug in the backup disk. 5 Deja Dup crashes at about the same timing as Nautilus opens the window for the mounted filesystem. Comment ----- I don't know if any particular step in this process is actually required. The backup device is a USB-attached HDD with a LUKS-encrypted partition containing an ext4 filesystem.
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached 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 to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping