GNOME Bugzilla – Bug 653465
[abrt] evolution-3.0.2-2.fc15: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
Last modified: 2012-09-04 19:10:09 UTC
Moving this from a downstream bug report: https://bugzilla.redhat.com/show_bug.cgi?id=716696 abrt version: 2.0.1 architecture: i686 cmdline: evolution component: evolution executable: /usr/bin/evolution kernel: 2.6.38.8-32.fc15.i686 os_release: Fedora release 15 (Lovelock) package: evolution-3.0.2-2.fc15 rating: 4 reason: Process /usr/bin/evolution was killed by signal 6 (SIGABRT) time: Sun Jun 26 14:12:59 2011 Core was generated by `evolution'. Program terminated with signal 6, Aborted.
+ Trace 227590
Thread 6 (Thread 0xb10ffb70 (LWP 15103))
I've reported this crash too in Fedora 15 [1]. Milan Crha asked: > Seeing all those warnings in .xsession-errors, I'm wondering whether you have > broken local summary of your imapx account. I would try to close evolution, > then rename > ~/.local/share/evolution/mail/<imapx-account> > to some other name, and then start evolution and let it fetch list of folders > from the server again. If something will go wrong, worse than now, then you can > rename the folder back. Indeed, the summary is probably broken, but in the end Evo fetches all messages again from scratch, and this fixes the problem (so I couldn't test this solution). This already happened to me a few times, but I can't tell why suddenly it chooses to do so, after not working for a while. Any idea how to debug this? It's hard since it only happens rarely... 1: https://bugzilla.redhat.com/show_bug.cgi?id=731684 and https://bugzilla.redhat.com/show_bug.cgi?id=731689
Thanks for taking the time to report this bug. However, you are using a version that is too old and not supported anymore. GNOME developers are no longer working on that version, so unfortunately there will not be any bug fixes for the version that you use. By upgrading to a newer version of GNOME you could receive bug fixes and new functionality. You may need to upgrade your Linux distribution to obtain a newer version of GNOME. Please feel free to reopen this bug if the problem still occurs with a newer version of GNOME.