Red Hat Bugzilla – Bug 802301
[abrt] evolution-data-server-3.2.3-2.fc16: _quicksort: Process /usr/libexec/e-calendar-factory was killed by signal 6 (SIGABRT)
Last modified: 2012-03-13 14:55:27 EDT
libreport version: 2.0.8
reason: Process /usr/libexec/e-calendar-factory was killed by signal 6 (SIGABRT)
time: Mon 27 Feb 2012 23:25:16 GMT
var_log_messages: Feb 27 23:25:22 z600 abrt: Saved core dump of pid 27340 (/usr/libexec/e-calendar-factory) to /var/spool/abrt/ccpp-2012-02-27-23:25:16-27340 (91234304 bytes)
backtrace: Text file, 51653 bytes
build_ids: Text file, 6970 bytes
dso_list: Text file, 14649 bytes
maps: Text file, 75076 bytes
smolt_data: Text file, 9315 bytes
Created attachment 569318 [details]
Created attachment 569319 [details]
Created attachment 569320 [details]
Created attachment 569321 [details]
Created attachment 569322 [details]
Thanks for a bug report. I suppose you are using an evolution-mapi calendar, but that's the most I see from the backtrace, because it's missing all the debug information for at least evolution-data-server and evolution-mapi.
If possible, could you write any steps how to reproduce this, and update the backtrace, please?
Good morning Milan Crha
Unfortunately I can't really provide an exact reproduction, these issues happen frequently but as I use the calendar so infrequently (partially due to the utter lack of stability), that I have not been able to keep a record of the individual steps that cause this.
Is there any way to ensure more information gathered the next time this happens?
I see. I do not like these "random" crashes.
(In reply to comment #7)
> Is there any way to ensure more information gathered the next time this
I'm afraid not, nothing in general. This may happen after some certain steps, thus try to remember what you did. If it's related to interaction with your calendar, then it can be things like reading meeting invites, accepting them, moving/deleting/editing events in the calendar. The worse is that it can depend also on a previous action (or actions) you did, like for example opening a meeting invitation email, moving to other mail, then back to invitation email and the e-calendar-factory goes down. These steps works fine for me, though.
Note the certain parts of evolution-mapi were changed for its 3.4.0 release, already included in current version (3.3.91) of Fedora 17, and also waiting for OpenChange 1.0 release, then maybe when the final Fedora 17 is out then you'll notice a little difference with your MAPI account.
> The worse is that it can depend also on a previous action (or actions) you did,
Oh don't I just know it, that's why I've pretty much given up on the calendar.
To be honest in my book it simply doesn't work, there are too many variables that result in a failure, hence I've given up even trying to track them down.
killall -9 evolution;evolution is a not so uncommon command on my desktop I'm afraid.
I look forward to Fedora 17, if nothing else I hope it will be easier to track down issues.
(In reply to comment #9)
> I look forward to Fedora 17, if nothing else I hope it will be easier to track
> down issues.
I agree, it'll be more current code, easier for chasing and fixing.