Version-Release number of selected component: evolution-3.10.4-1.fc20 Additional info: reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: evolution crash_function: set_length executable: /usr/bin/evolution kernel: 3.13.5-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 set_length at dbus-string.c:390 #1 _dbus_string_set_length at dbus-string.c:786 #2 dbus_message_new_empty_header at dbus-message.c:1177 #3 dbus_message_new_signal at dbus-message.c:1359 #4 emit_event at event.c:469 #5 state_event_listener at event.c:638 #14 g_object_notify_queue_thaw at gobject.c:292 #15 g_object_set_property at gobject.c:2330 #16 on_source_notify at gbinding.c:389 #22 g_object_notify_by_spec_internal at gobject.c:1141
Created attachment 870760 [details] File: backtrace
Created attachment 870761 [details] File: cgroup
Created attachment 870762 [details] File: core_backtrace
Created attachment 870763 [details] File: dso_list
Created attachment 870764 [details] File: environ
Created attachment 870765 [details] File: exploitable
Created attachment 870766 [details] File: limits
Created attachment 870767 [details] File: maps
Created attachment 870768 [details] File: open_fds
Created attachment 870769 [details] File: proc_pid_status
Created attachment 870770 [details] File: var_log_messages
Thanks for a bug report. I see from the backtrace that your evolution was going online, probably after you connected your computer to a network, when also a change was notified from "/org/a11y/atspi/accessible/" through D-Bus, which is served in three threads for different interfaces. One of the threads, in the middle of a D-Bus call crashed. I do not see from the backtrace why, though. Evolution uses glib2's GDBus, thus I move it there for better investigation.
the crash is in libdbus, actually
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora 'version' of '20'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 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 this bug is closed as described in the policy above. 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.