Red Hat Bugzilla – Bug 1029248
[abrt] evolution-3.10.1-1.fc20: e_table_header_get_column_by_spec: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Last modified: 2013-11-15 14:15:51 EST
Description of problem:
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (7 frames)
#0 e_table_header_get_column_by_spec at e-table-header.c:487
#1 ml_sort_uids_by_tree at message-list.c:5216
#2 message_list_regen_thread at message-list.c:5448
#3 run_in_thread at gsimpleasyncresult.c:871
#4 io_job_thread at gioscheduler.c:89
#5 g_task_thread_pool_thread at gtask.c:1245
#7 g_thread_proxy at gthread.c:798
Created attachment 822698 [details]
Created attachment 822699 [details]
Created attachment 822700 [details]
Created attachment 822701 [details]
Created attachment 822702 [details]
Created attachment 822703 [details]
Created attachment 822704 [details]
Created attachment 822705 [details]
Created attachment 822706 [details]
Created attachment 822707 [details]
Created attachment 822708 [details]
Thanks for a bug report. Does this crash each evolution start for you, or it happened only once? It may also depend in which folder you stay, or enter. The code tries to apply some sorting you've setup on the folder, and it fails when getting the set data column, according to the backtrace.
(In reply to Milan Crha from comment #12)
> Thanks for a bug report. Does this crash each evolution start for you, or it
> happened only once? It may also depend in which folder you stay, or enter.
> The code tries to apply some sorting you've setup on the folder, and it
> fails when getting the set data column, according to the backtrace.
I have only senn this oence. I can not repeat. I was updateing whit yum just before.
Thanks for the update. Good and pity at the same time that it happened to you only once. I think it is possible that it's more or less related to the update in the background. Let's close this for now, but please feel free to reopen or simply file new bugs, if/when you'll find any.