Ubuntu
evolution package

Evolution crash with SIGSEGV

Bug #385867 reported by Han Pilmeyer on 2009-06-11

This bug report is a duplicate of: Bug #287136: evolution crashed with SIGSEGV in e_flag_set(). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	evolution (Ubuntu)	Invalid	Medium	Ubuntu Desktop Bugs

Bug Description

Binary package hint: evolution

I wasn't doing anything in particular with evolution when it crashed with SIGSEGV. However I do have schedules where I process new messages from a local store and imap and filter these. So it could have been during one of those actions. This happens about ones a day. Attached is the stack backtrace of all threads.

Evolution was very stable for me under 8.10. This problem started as soon as I upgraded to Jaunty 9.04. Currently using evolution 2.26.1-0ubuntu2.

I'm currently trying to run evolution under valgrind, but I'm not sure that will be a workable option as it seems to slow evolution down to a crawl.

Please let me know what I can do to help fix this issue.

Revision history for this message

Han Pilmeyer (pilux) wrote on 2009-06-11:

Backtrace for all threads Edit (14.2 KiB, text/plain)

Revision history for this message

Sebastien Bacher (seb128) wrote on 2009-06-11:

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a '.crash' file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.

If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash in a terminal - where _my_crash_report.crash is the crash you would like to report.
I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.