Description of problem: I added my Google account to GNOME in the Online Accounts settings. I then opened Evolution and read some of my Gmail messages. I closed Evolution and removed my Google account from Online Accounts. Within a few seconds of removing my Google account, Evolution crashed. Version-Release number of selected component: evolution-data-server-3.10.4-1.fc20 Additional info: reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: /usr/libexec/evolution-calendar-factory crash_function: block_source executable: /usr/libexec/evolution-calendar-factory kernel: 3.13.3-201.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (3 frames) #0 block_source at gmain.c:2958 #6 gdbus_shared_thread_func at gdbusprivate.c:278 #7 g_thread_proxy at gthread.c:798
Created attachment 865849 [details] File: backtrace
Created attachment 865850 [details] File: cgroup
Created attachment 865851 [details] File: core_backtrace
Created attachment 865852 [details] File: dso_list
Created attachment 865853 [details] File: environ
Created attachment 865854 [details] File: exploitable
Created attachment 865855 [details] File: limits
Created attachment 865856 [details] File: maps
Created attachment 865857 [details] File: open_fds
Created attachment 865858 [details] File: proc_pid_status
Created attachment 865859 [details] File: var_log_messages
Thanks for a bug report. I tried to reproduce this, but no luck, the evolution-calendar-factory doesn't crash for me, when I repeat your steps from comment #0. Did you get this crash only once, or you can reliably reproduce this? I ask also, because the backtrace doesn't show anything directly related to evolution-calendar-factory code, the process crashed in GLib's code, which doesn't mean much, if there was a memory corruption issue involved (like if some part of the process wrote in an already freed memory).
I have been able to reproduce the crash, but only one time out of several attempts. This is what I did: 1. Add Google account in Online Accounts settings. 2. Open Evolution. 3. Open an email message. 4. Close Evolution. 5. Remove Google account. Evolution crashed within a few seconds of removing the Google account. I then decided to record a video of the crash, but I haven't been able to reproduce the crash after several attempts (including a reboot).
Thanks for the update. I suspect the account removal was done while the associated Google calendar was still being updated, which led to this crash, but I do not see any exact signs of it in the backtrace (there are shown two running CalDAV calendars, waiting for some work, but nothing else related to Google calendar (evolution uses CalDAV to connect Google calendars)).
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.