Bug 1181079

Summary: [abrt] evolution: camel_flag_list_copy(): evolution killed by SIGABRT
Product: [Fedora] Fedora Reporter: Gwendal <ezwen-redhatbugzilla>
Component: evolutionAssignee: Milan Crha <mcrha>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 21CC: ezwen-redhatbugzilla, lucilanga, mbarnes, mcrha, tpopela
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/60355744397da0ac3fb21853fd6f3cb3f29c5c6b
Whiteboard: abrt_hash:7f05733c61e3b16d63d7d789da65476958f2879b
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-04 14:08:06 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Gwendal 2015-01-12 10:48:07 UTC 
Version-Release number of selected component:
evolution-3.12.9-1.fc21

Additional info:
reporter:       libreport-2.3.0
backtrace_rating: 4
cmdline:        evolution
crash_function: camel_flag_list_copy
executable:     /usr/bin/evolution
kernel:         3.17.8-300.fc21.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (9 frames)
 #7 camel_flag_list_copy at camel-folder-summary.c:4200
 #8 imapx_update_user_flags at camel-imapx-utils.c:269
 #9 imapx_update_message_info_flags at camel-imapx-utils.c:327
 #10 imapx_untagged_fetch at camel-imapx-server.c:2307
 #11 imapx_untagged at camel-imapx-server.c:3041
 #12 imapx_step at camel-imapx-server.c:3432
 #13 imapx_ready_to_read at camel-imapx-server.c:7673
 #18 imapx_parser_thread at camel-imapx-server.c:7789
 #19 g_thread_proxy at gthread.c:764
Comment 1 Gwendal 2015-01-12 10:48:10 UTC 
Created attachment 979066 [details]
File: backtrace
Comment 2 Gwendal 2015-01-12 10:48:11 UTC 
Created attachment 979067 [details]
File: cgroup
Comment 3 Gwendal 2015-01-12 10:48:13 UTC 
Created attachment 979068 [details]
File: core_backtrace
Comment 4 Gwendal 2015-01-12 10:48:14 UTC 
Created attachment 979069 [details]
File: dso_list
Comment 5 Gwendal 2015-01-12 10:48:15 UTC 
Created attachment 979070 [details]
File: environ
Comment 6 Gwendal 2015-01-12 10:48:16 UTC 
Created attachment 979071 [details]
File: limits
Comment 7 Gwendal 2015-01-12 10:48:18 UTC 
Created attachment 979072 [details]
File: maps
Comment 8 Gwendal 2015-01-12 10:48:19 UTC 
Created attachment 979073 [details]
File: open_fds
Comment 9 Gwendal 2015-01-12 10:48:20 UTC 
Created attachment 979074 [details]
File: proc_pid_status
Comment 10 Gwendal 2015-01-12 10:48:21 UTC 
Created attachment 979075 [details]
File: var_log_messages
Comment 11 Milan Crha 2015-01-26 18:41:14 UTC 
Thanks for a bug report. I do not see much information from the backtrace, it shows where exactly the crash happened, but not why, like what caused it. By any chance, do you have any steps for a reproducer, please?
Comment 12 Gwendal 2015-01-26 19:07:33 UTC 
Hi! I am very sorry, but I don't have any kind of information regarding the reason of the crash, or on how to reproduce it. I hoped the backtrace would be enough and interesting... I'll try to find more information next time it happens (if it does)!
Comment 13 Milan Crha 2015-02-04 14:08:06 UTC 
Thanks for the update. The backtrace is clean and interesting, but to have a reproducer and possibly know what caused it is necessary to properly address this. It can also be that some part of the code rewrote memory which it shouldn't touch, making this crash as a side-effect of the faulty code. I'm closing this for now, but please feel free to reopen, if you get any new information, or just file a new bug reports.
Comment 14 Gwendal 2015-02-11 09:06:20 UTC 
Another user experienced a similar problem:

Right after Fedora started, I started Evolution, which instantly crashed.

reporter:       libreport-2.3.0
backtrace_rating: 4
cmdline:        evolution
crash_function: camel_flag_list_copy
executable:     /usr/bin/evolution
kernel:         3.18.5-201.fc21.x86_64
package:        evolution-3.12.10-1.fc21
reason:         evolution killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            1000