Bug 1158056

Summary: [abrt] evolution: magazine_chain_pop_head(): evolution killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Artur Flinta <aflinta>
Component: evolutionAssignee: Milan Crha <mcrha>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 21CC: lucilanga, mbarnes, mcrha, tpopela
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/baec95f9d48189acb4a9e9b0acace927a3986e78
Whiteboard: abrt_hash:7adfd265ae56226ddbca7f785fa8ece813eaad76
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-30 06:35:37 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: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Artur Flinta 2014-10-28 12:59:52 UTC 
Version-Release number of selected component:
evolution-3.12.7-1.fc21

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

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 magazine_chain_pop_head at gslice.c:539
 #1 thread_memory_magazine1_alloc at gslice.c:842
 #2 g_slice_alloc at gslice.c:998
 #3 g_slist_prepend at gslist.c:254
 #4 g_object_notify_queue_add at gobject.c:305
 #5 object_set_property at gobject.c:1424
 #6 g_object_new_internal at gobject.c:1828
 #7 g_object_new_valist at gobject.c:2034
 #9 e_soap_message_new_from_uri at e-soap-message.c:390
 #10 e_soap_message_new at e-soap-message.c:340

Potential duplicate: bug 701604
Comment 1 Artur Flinta 2014-10-28 12:59:55 UTC 
Created attachment 951387 [details]
File: backtrace
Comment 2 Artur Flinta 2014-10-28 12:59:57 UTC 
Created attachment 951388 [details]
File: cgroup
Comment 3 Artur Flinta 2014-10-28 12:59:58 UTC 
Created attachment 951389 [details]
File: core_backtrace
Comment 4 Artur Flinta 2014-10-28 13:00:00 UTC 
Created attachment 951390 [details]
File: dso_list
Comment 5 Artur Flinta 2014-10-28 13:00:01 UTC 
Created attachment 951391 [details]
File: environ
Comment 6 Artur Flinta 2014-10-28 13:00:03 UTC 
Created attachment 951392 [details]
File: exploitable
Comment 7 Artur Flinta 2014-10-28 13:00:04 UTC 
Created attachment 951393 [details]
File: limits
Comment 8 Artur Flinta 2014-10-28 13:00:06 UTC 
Created attachment 951394 [details]
File: maps
Comment 9 Artur Flinta 2014-10-28 13:00:07 UTC 
Created attachment 951395 [details]
File: open_fds
Comment 10 Artur Flinta 2014-10-28 13:00:09 UTC 
Created attachment 951396 [details]
File: proc_pid_status
Comment 11 Artur Flinta 2014-10-28 13:00:10 UTC 
Created attachment 951397 [details]
File: var_log_messages
Comment 12 Milan Crha 2014-10-29 08:01:16 UTC 
Thanks for a bug report. I guess this is related to your bug #1158055. Did it happen after a similar circumstances (after sending a message through your EWS account)?
Comment 13 Artur Flinta 2014-10-29 08:20:28 UTC 
Well, yes it's possible, cause I'm using evo only for EWS :)
Comment 14 Milan Crha 2014-10-30 06:35:37 UTC 
Okay. Let's cover this under that other bug report too.

*** This bug has been marked as a duplicate of bug 1158055 ***