GNOME Bugzilla – Bug 270160
evolution-exchange storage crashing on calandar
Last modified: 2004-12-09 18:12:39 UTC
Please fill in this template when reporting a bug, unless you know what you are doing. Description of Problem: Whenever the calendar sync checkbox is clicked, evolution-data-storage segfaults (see output below). Steps to reproduce the problem: 1. Open evolution. 2. Click on calendar. 3. Check box next to "calendar." Actual Results: Crash Expected Results: Sync with Exchange server and display of calendar. How often does this happen? Every time. Additional Information: Here's the console output: Evolution Exchange Storage up and running (evolution-exchange-storage:17228): libedata-cal-WARNING **: e-data-cal-view.c:249: Starting new query (evolution-exchange-storage:17228): libedata-cal-WARNING **: e-data-cal-view.c:249: Starting new query (evolution-exchange-storage:17228): libecal-CRITICAL **: file e-cal-component.c: line 2321 (e_cal_component_get_dtstart): assertion `priv->icalcom p != NULL' failed (evolution-exchange-storage:17228): libecal-CRITICAL **: file e-cal-component.c: line 2205 (e_cal_component_get_dtend): assertion `priv->icalcomp != NULL' failed (evolution-exchange-storage:17228): libecal-CRITICAL **: file e-cal-component.c: line 3396 (e_cal_component_has_rdates): assertion `priv->icalcomp != NULL' failed (evolution-exchange-storage:17228): libecal-CRITICAL **: file e-cal-component.c: line 3489 (e_cal_component_has_rrules): assertion `priv->icalcomp != NULL' failed (evolution-exchange-storage:17228): libecal-CRITICAL **: file e-cal-component.c: line 2677 (e_cal_component_has_exdates): assertion `priv->icalcom p != NULL' failed (evolution-exchange-storage:17228): libecal-CRITICAL **: file e-cal-component.c: line 2838 (e_cal_component_has_exrules): assertion `priv->icalcom p != NULL' failed free(): invalid pointer 0xbffff428! Multiple segmentation faults occurred; can't display error dialog
Can you please attach the backtrace of exchange-storage process when it crashes? See http://www.gnome.org/projects/evolution/bugs.shtml for details.
(gdb) thread apply all bt
+ Trace 53138
Thread 1 (Thread -1230736096 (LWP 2551))
Another note. This used to work on my system. But even in the past, about 1/4 times it the exchange connector would consume all available memory and swap and take me into swapping hell on calendar access. Sometimes I was able to type --force-shutdown and then "rm -rf .evolution." This would get me going again until the next time it happened. Now it just crashes all the time.
Solved! I happened to check the logs for Outlook syncing with my Treo and noticed that it was choking on something too. It was a meeting that had sideways text that, I believe, has something to do with Crossover office accessing the meeting. From the Codeweavers site (Crossover): "This is due to a bug in the way CrossOver handles text using the Richedit library." So, I deleted the meeting in Real[tm] Outlook and viola, no more Evolution choking. I only with that there had been a better way to debug this from Evolution.