Hide Forgot
abrt version: 1.1.17 architecture: x86_64 Attached file: backtrace, 9255 bytes cmdline: deja-dup --backup --display=:0.0 comment: I hve tried with and without the --display=:0.0 or --display=0.0 or --display=0 but nothing changes component: deja-dup Attached file: coredump, 3940352 bytes crash_function: deja_dup_operation_start_finish executable: /usr/bin/deja-dup kernel: 2.6.35.11-83.fc14.x86_64 package: deja-dup-16.1.1-1.fc14 rating: 4 reason: Process /usr/bin/deja-dup was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1301485921 uid: 500 How to reproduce ----- 1. Launched deja-dup with the --backup flag to run it from a cronjob It works fine if launched by a terminal, but not from my user crontab
Created attachment 488748 [details] File: backtrace
I forgot to mention the error reported by the cron mail ** (deja-dup:27034): WARNING **: CommonUtils.vala:159: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Not running within active session) ** (deja-dup:27034): WARNING **: AssistantOperation.vala:337: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Not running within active session) ** (deja-dup:27034): WARNING **: Operation.vala:91: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Not running within active session) ** (deja-dup:27034): CRITICAL **: deja_dup_backend_set_mount_op: assertion `self != NULL' failed (deja-dup:27034): GLib-GObject-WARNING **: invalid (NULL) pointer instance (deja-dup:27034): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
The crash is no longer present in 17.92, so I'd say this bug could be closed. But it still won't work from cron. Deja Dup needs access to your dbus too and your user session. I don't recommend trying to cron it. It has its own built in launch-after-a-certain-amount-of-time logic (though admittedly not as good as cron's).
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