Bug 1159424

Summary: [abrt] evolution: magazine_chain_pop_head(): evolution killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Igor Gnatenko <ignatenko>
Component: evolutionAssignee: Milan Crha <mcrha>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: antonio.montagnani, fedbzville, hlx98007, ignatenko, lucilanga, mbarnes, mcrha, tpopela, yuriyku
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/ac0de1203fe6276f39ca2591dc65c195b0275411
Whiteboard: abrt_hash:7adfd265ae56226ddbca7f785fa8ece813eaad76
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-07 09:07:52 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 Igor Gnatenko 2014-10-31 22:42:28 UTC 
Version-Release number of selected component:
evolution-3.13.7-1.fc22

Additional info:
reporter:       libreport-2.3.0
backtrace_rating: 4
cmdline:        evolution jobcroc?subject=Python-%D1%80%D0%B0%D0%B7%D1%80%D0%B0%D0%B1%D0%BE%D1%82%D1%87%D0%B8%D0%BA
crash_function: magazine_chain_pop_head
executable:     /usr/bin/evolution
kernel:         3.17.1-302.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:1808
 #7 g_object_new_valist at gobject.c:2034
 #9 g_network_address_parse_uri at gnetworkaddress.c:757
 #10 g_proxy_address_enumerator_constructed at gproxyaddressenumerator.c:581

Potential duplicate: bug 701604
Comment 1 Igor Gnatenko 2014-10-31 22:42:32 UTC 
Created attachment 952621 [details]
File: backtrace
Comment 2 Igor Gnatenko 2014-10-31 22:42:33 UTC 
Created attachment 952622 [details]
File: cgroup
Comment 3 Igor Gnatenko 2014-10-31 22:42:35 UTC 
Created attachment 952623 [details]
File: core_backtrace
Comment 4 Igor Gnatenko 2014-10-31 22:42:37 UTC 
Created attachment 952624 [details]
File: dso_list
Comment 5 Igor Gnatenko 2014-10-31 22:42:38 UTC 
Created attachment 952625 [details]
File: environ
Comment 6 Igor Gnatenko 2014-10-31 22:42:39 UTC 
Created attachment 952626 [details]
File: exploitable
Comment 7 Igor Gnatenko 2014-10-31 22:42:40 UTC 
Created attachment 952627 [details]
File: limits
Comment 8 Igor Gnatenko 2014-10-31 22:42:42 UTC 
Created attachment 952628 [details]
File: maps
Comment 9 Igor Gnatenko 2014-10-31 22:42:44 UTC 
Created attachment 952629 [details]
File: open_fds
Comment 10 Igor Gnatenko 2014-10-31 22:42:45 UTC 
Created attachment 952630 [details]
File: proc_pid_status
Comment 11 Igor Gnatenko 2014-10-31 22:42:47 UTC 
Created attachment 952631 [details]
File: var_log_messages
Comment 12 Milan Crha 2014-11-03 08:31:23 UTC 
Thanks for a bug report. I see from the backtrace that the crash is most likely caused by a memory corruption (for example some code could access already freed memory), when evolution was resolving a server address and sending a message. Do you have any steps for a reproducer, please? Also, do you use any proxy server for connection, either system-wide configured, or configured inside Evolution, at Edit->Preferences->Network Preferences?

I'd guess from the above backtrace and information that you:
a) clicked some "mailto:" link to send a message
b) a message composer opened, where you filled the message body and such
c) sent the message, when the crash happened

I also guess that the evolution was not running before doing this.
Comment 13 Jaroslav Reznik 2015-03-03 16:27:34 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Comment 14 Igor Gnatenko 2016-07-07 09:07:52 UTC 
Can't reproduce anymore.