Version-Release number of selected component: evolution-data-server-3.10.4-3.fc20 Additional info: reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: /usr/libexec/evolution-calendar-factory crash_function: unblock_source executable: /usr/libexec/evolution-calendar-factory kernel: 3.13.7-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (3 frames) #0 unblock_source at gmain.c:2991 #6 gdbus_shared_thread_func at gdbusprivate.c:278 #7 g_thread_proxy at gthread.c:798
Created attachment 880513 [details] File: backtrace
Created attachment 880514 [details] File: cgroup
Created attachment 880515 [details] File: core_backtrace
Created attachment 880516 [details] File: dso_list
Created attachment 880517 [details] File: environ
Created attachment 880518 [details] File: exploitable
Created attachment 880519 [details] File: limits
Created attachment 880520 [details] File: maps
Created attachment 880521 [details] File: open_fds
Created attachment 880522 [details] File: proc_pid_status
Created attachment 880523 [details] File: var_log_messages
Thanks for a bug report. I do not see from the backtrace what could cause the crash, more importantly the shown code is only from the core GLib/GIO code, which is unlikely that this common code would be buggy, thus I think there happened some sort of memory corruption (like when some part of the code writes to an already freed memory). This might be caused by some previous usage of the calendar factory, which can be done like by direct user requests (like when viewing calendar(s) in Evolution or in the GNOME Shell's UI (clock applet), or by a periodic update of your calendars. Do you remember what you did with your calendars before the crash, if anything, please? I do not expect this being reliably reproducible, right?
I usually work with calendars on my phone, so I doubt I was actively interacting with the calendar in Evolution. So my guess is that it happens when some background action like a refresh occurs. I do have the gnome-shell clock applet active. It happens fairly frequently but I haven't identified a reliable way to reproduce it. Heavy network traffic seems to increase the frequency. I will keep an eye on it and see if I can reproduce it or correlate it with something.
Aha. I didn't notice it before, but the network traffic can have an impact on this, or at least be partly related. The backtrace shows, that one thread is going to check what is new in your Google calendar, and it is currently in a name resolution of "www.google.com". Another thread is also working with this calendar, creating a new view here. These views are meant to give the creator a live updates on new/changed/removed events which satisfy certain criteria, like events for today. This is used in evolution-alarm-notify (and evolution itself of course), and I'm pretty sure in gnome-shell's clock applet as well. If this happened due to some use-after-free, then probably a valgrind output may help to identify what happened. If you can, please install valgrind and debuginfo packages for evolution-data-server, libsoup and glib2 - make sure the versions will match their binary package versions. Then open a terminal and run these commands: $ export G_DEBUG=gc-friendly $ G_SLICE=always-malloc valgrind --num-callers=50 \ /usr/libexec/evolution-calendar-factory -w &>log.txt Then stop and run in another terminal the evolution-alarm-notify process, just to make sure it'll be connected to the newly run calendar factory. The process is hidden in /usr/libexec/evolution/3.10/ directory.
*** Bug 1086096 has been marked as a duplicate of this bug. ***
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
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.