Bug 1202741

Summary: [abrt] evolution: resort_node(): evolution killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Milan Bouchet-Valat <nalimilan>
Component: evolutionAssignee: Milan Crha <mcrha>
Status: CLOSED RAWHIDE 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/90ae1e688666f0b4395a77edec8dbbfdd6e47c02
Whiteboard: abrt_hash:0010189fcfb51e18aa47eaa4bf2ab679caa60976
Fixed In Version: evolution-3.16.1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-24 08:11:43 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

Description Milan Bouchet-Valat 2015-03-17 11:04:42 UTC 
Description of problem:
Just sent an e-mail (which was apparently successfully saved to the Sent box).

Version-Release number of selected component:
evolution-3.12.11-1.fc21

Additional info:
reporter:       libreport-2.3.0
backtrace_rating: 4
cmdline:        evolution
crash_function: resort_node
executable:     /usr/bin/evolution
kernel:         3.18.9-200.fc21.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000
var_log_messages: [System Logs]:\n-- Logs begin at sam. 2014-03-15 00:26:09 CET, end at mar. 2015-03-17 11:41:51 CET. --

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 resort_node at e-tree-table-adapter.c:200
 #2 e_tree_table_adapter_set_sort_info at e-tree-table-adapter.c:1160
 #3 e_tree_set_state_object at e-tree.c:1401
 #4 gal_view_etable_attach_tree at gal-view-etable.c:255
 #5 mail_paned_display_view_cb at e-mail-paned-view.c:257
 #6 mail_paned_view_update_view_instance at e-mail-paned-view.c:952
 #10 g_signal_emit_by_name at gsignal.c:3405
 #15 mail_reader_emit_folder_loaded at e-mail-reader.c:2960
 #16 mail_reader_message_list_built_cb at e-mail-reader.c:2970
 #17 _g_closure_invoke_va at gclosure.c:831
Comment 1 Milan Bouchet-Valat 2015-03-17 11:04:45 UTC 
Created attachment 1002754 [details]
File: backtrace
Comment 2 Milan Bouchet-Valat 2015-03-17 11:04:46 UTC 
Created attachment 1002755 [details]
File: cgroup
Comment 3 Milan Bouchet-Valat 2015-03-17 11:04:47 UTC 
Created attachment 1002756 [details]
File: core_backtrace
Comment 4 Milan Bouchet-Valat 2015-03-17 11:04:49 UTC 
Created attachment 1002757 [details]
File: dso_list
Comment 5 Milan Bouchet-Valat 2015-03-17 11:04:49 UTC 
Created attachment 1002758 [details]
File: environ
Comment 6 Milan Bouchet-Valat 2015-03-17 11:04:50 UTC 
Created attachment 1002759 [details]
File: exploitable
Comment 7 Milan Bouchet-Valat 2015-03-17 11:04:51 UTC 
Created attachment 1002760 [details]
File: limits
Comment 8 Milan Bouchet-Valat 2015-03-17 11:04:53 UTC 
Created attachment 1002761 [details]
File: maps
Comment 9 Milan Bouchet-Valat 2015-03-17 11:04:54 UTC 
Created attachment 1002762 [details]
File: open_fds
Comment 10 Milan Bouchet-Valat 2015-03-17 11:04:55 UTC 
Created attachment 1002763 [details]
File: proc_pid_status
Comment 11 Milan Crha 2015-03-19 06:23:27 UTC 
Thanks for a bug report. I do not think there is anything truly odd in the code, at least not in this particular part, even a safety check for non-NULL 'node' variable could be added. That would be just a workaround. I'd guess that you face a fallout of bug #1192773.
Comment 12 Milan Bouchet-Valat 2015-03-19 09:07:00 UTC 
Sorry, I don't have a reproducer. Maybe the safety would be good until the root cause is identified.
Comment 13 Milan Bouchet-Valat 2015-03-19 09:07:26 UTC 
s/safety/safety check/
Comment 14 Milan Crha 2015-03-24 08:11:43 UTC 
Right, let's try that way. I made the change [1] for 3.17.1+ and 3.16.1+. I'm closing this for now, even the root cause was not found here. We can watch the console and see whether it'll repeat again at all.

[1] https://git.gnome.org/browse/evolution/commit/?id=c878574