Created attachment 974959 [details] coredumpctl gdb backtrace Description of problem: Repeated crash starting /usr/libexec/evolution-calendar-factory causing system to lock up with 100% CPU and IO as systemd processes the core dumps. Version-Release number of selected component (if applicable): The problem started occurring with evolution-data-server-3.12.8-1.fc21.x86_64 but did not occur with evolution-data-server-3.12.7.1-1.fc21.x86_64. How reproducible: Always happens Steps to Reproduce: 1. Start with GNOME Desktop (or start Evolution manually in KDE) 2. 3. Actual results: Evolution reports that the "The calendar backend servicing "Personal" has quit unexpectedly." Expected results: Evolution starts up and allows my calendars to be viewed. Additional info: I have a personal calendar stored in Evolution plus 3 external ical calendars from Google and Last.fm
I've discovered the underlying cause of the crash. It looks like the GNOME Online Accounts had a set of Google credentials. These had expired. Re-logging in cause the crash in the evolution calendar to stop happening. During the investigation I had removed all of the evolution data files ( as per https://help.gnome.org/users/evolution/3.12/data-storage.html.en) while logged in through a text console. The crash kept happening.
Thanks for a bug report. This particular one had been reported already, thus I'm marking it as a duplicate. I also updated the associated upstream bug report with your comments and investigation results. *** This bug has been marked as a duplicate of bug 1136778 ***