Description of problem: Not sure Version-Release number of selected component: evolution-data-server-3.10.2-2.fc20 Additional info: reporter: libreport-2.1.9 backtrace_rating: 3 cmdline: /usr/libexec/evolution-calendar-factory crash_function: g_type_check_instance executable: /usr/libexec/evolution-calendar-factory kernel: 3.11.10-301.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 g_type_check_instance at gtype.c:4080 #1 g_signal_handler_disconnect at gsignal.c:2580 #2 on_connection_disconnected at gdbusnamewatching.c:260 #3 ffi_call_unix64 at ../src/x86/unix64.S:76 #4 ffi_call at ../src/x86/ffi64.c:522 #5 g_cclosure_marshal_generic at gclosure.c:1454 #10 emit_closed_in_idle at gdbusconnection.c:1389 #14 g_main_context_iteration at gmain.c:3774 #15 dconf_gdbus_worker_thread at dconf-gdbus-thread.c:81 #16 g_thread_proxy at gthread.c:798
Created attachment 888687 [details] File: backtrace
Created attachment 888688 [details] File: cgroup
Created attachment 888689 [details] File: core_backtrace
Created attachment 888690 [details] File: dso_list
Created attachment 888691 [details] File: environ
Created attachment 888692 [details] File: exploitable
Created attachment 888693 [details] File: limits
Created attachment 888694 [details] File: maps
Created attachment 888695 [details] File: open_fds
Created attachment 888696 [details] File: proc_pid_status
Created attachment 888697 [details] File: var_log_messages
Thanks for a bug report. I'm also not sure what could cause the trouble, the only thing I see is that the evolution-source-registry was probably closing itself, while the dconf_gdbus_worker_thread recognized a disconnect from a related D-Bus service and it tried to react on it. It is most likely accessing already freed memory, thus it caused a crash. I guess this was more like a one-time crash, right? I'm reassigning this to dconf anyway, to check whether they disconnect themself from the GDBusConnection on the dispose, thus the signal callback is not invoked on the already freed object.
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.