GNOME Bugzilla – Bug 663110
Crash on copy events between calendars
Last modified: 2014-06-17 14:13:31 UTC
Using Evolution 3.X as installed/upgraded by the Ubuntu 11.10 updater. Two calendars - one local, one DAV. DAV configured to sync with Google calendar, confirmed by creating a test event. Goal is to copy everything from local to DAV. Right click on local calendar, select "Copy", dialog pops up to selection destination of copy. Select the DAV calendar, then OK. Evolution hangs unresponsive for about a minute, then crashes. Running on dual core 3.2 GHz with 4 GB RAM, Ubuntu 11.10.
Upon restarting Evolution after the crash, nothing has been copied to the DAV calendar. Attempting to copy individual events also fails - silently, no message, no crash, but they don't copy. That is: right-click on event in local calendar, select "copy to...", dialog pops up, select DAV calendar, then OK. Nothing happens - no error, no crash, but event is not copied.
Thanks for taking the time to report this bug. Does Ubuntu 11.10 really include 3.0? I hope that you use 3.2 instead... If so, please edit the Version field of this report. Without a stack trace from the crash it's very hard to determine what caused it. Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
When I updated Ubuntu from 11.04 to 11.10, Evolution updated from 2.x to 3.x. I don't have access to my Ubuntu system right now so I can't check, but the version of Evolution is whatever is the latest as per the Ubuntu Software Center and update manager. When I get home tonight I'll get a stack strace and exact version #.
Details: Evolution 3.2.0. NOTE: before starting this, I have verified the target CalDAV calendar is working. I created and deleted events in Google, and in Evolution, and each updates the other. --- Behavior after selecting the calendar to copy into: A series of dialogs appear each saying either this: --- Cannot create object Cannot create calendar object: Unexpected HTTP status code 409 returned (Can only store an event with a newer DTSTAMP) --- or this: --- Cannot create object Cannot create calendar object: Authentication Failed --- Perhaps the first error message is related to copying recurring events? Just a guess. A new dialog appears every 15-20 seconds while the app is non-responsive, and they pile on top of each other. If I click the "Close" button on any of these dialogs, then the application crashes a minute or so after clicking it. If I ignore them, they build up for several minutes... still running.
More Info: It does eventually crash even if I don't click on the dialogs. Due to the HTTP errors above, I tried copying that entire calendar to a local calendar. Entire Evolution screen goes grey and it hangs for several minutes, then crashes. So the above HTTP errors, while suggestive that it's a CalDAV problem, are not the root cause since this same error occurs even when copying to another local calendar. I installed the debug symbols and bug buddy, but bug buddy never kicked in when Evolution crashed, so I don't have a stack trace.
Confirming, when copying from one local calendar to a new one. The first the calendar factory process crashed with this backtrace:
+ Trace 229683
Thread 2 (Thread 0x7fa3cb7fe700 (LWP 23529))
After some time evolution itself crashed as well, with this backtrace (note both traces are from current git mater, which is before 3.3.90 release). The part with g_main_context_dispatch repeats down to frame 199, and gdb doesn't show more. Backtrace itself:
+ Trace 229684
Created attachment 207848 [details] [review] evo patch for evolution; Little typo in the code, the destination calendar had been opened recursively forever, doing also repeated copies. After fixing this the calendar factory does not crash as well.
Created commit 1101e93 in evo master (3.3.90+)
*** Bug 664614 has been marked as a duplicate of this bug. ***