Bug 908152

Summary: [abrt] evolution-3.4.4-2.fc17: e_table_sorting_utils_sort: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Louis van Dyk <louis>
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: lucilanga, mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:eed8d50a3502cdeaba69dea662b2551b2c9449b7
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-06 08:00:01 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: core_backtrace
none
File: environ
none
File: backtrace
none
File: limits
none
File: gconf_subtree
none
File: cgroup
none
File: smolt_data
none
File: executable
none
File: xsession_errors
none
File: maps
none
File: dso_list
none
File: proc_pid_status
none
File: var_log_messages
none
File: open_fds none

Description Louis van Dyk 2013-02-06 02:41:47 UTC 
Description of problem:
I was moving items one-by-one from the local "On this computer" Evolution Calendar, to the remote EWS Exchange 2010 calendar.  A number had succeeded, but this one time Evolution crashed.  I re-opened it and am moving items again, with out it crashing again.

Version-Release number of selected component:
evolution-3.4.4-2.fc17

Additional info:
libreport version: 2.0.18
abrt_version:   2.0.18
backtrace_rating: 4
cmdline:        evolution
crash_function: e_table_sorting_utils_sort
kernel:         3.7.3-101.fc17.x86_64

truncated backtrace:
:Thread no. 1 (4 frames)
: #6 e_table_sorting_utils_sort at e-table-sorting-utils.c:165
: #7 ets_sort at e-table-sorted.c:325
: #8 ets_sort_idle at e-table-sorted.c:112
: #13 gtk_main at gtkmain.c:1161
Comment 1 Louis van Dyk 2013-02-06 02:41:51 UTC 
Created attachment 693633 [details]
File: core_backtrace
Comment 2 Louis van Dyk 2013-02-06 02:41:54 UTC 
Created attachment 693634 [details]
File: environ
Comment 3 Louis van Dyk 2013-02-06 02:41:58 UTC 
Created attachment 693635 [details]
File: backtrace
Comment 4 Louis van Dyk 2013-02-06 02:42:02 UTC 
Created attachment 693636 [details]
File: limits
Comment 5 Louis van Dyk 2013-02-06 02:42:06 UTC 
Created attachment 693637 [details]
File: gconf_subtree
Comment 6 Louis van Dyk 2013-02-06 02:42:09 UTC 
Created attachment 693638 [details]
File: cgroup
Comment 7 Louis van Dyk 2013-02-06 02:42:11 UTC 
Created attachment 693639 [details]
File: smolt_data
Comment 8 Louis van Dyk 2013-02-06 02:42:14 UTC 
Created attachment 693640 [details]
File: executable
Comment 9 Louis van Dyk 2013-02-06 02:42:19 UTC 
Created attachment 693641 [details]
File: xsession_errors
Comment 10 Louis van Dyk 2013-02-06 02:42:23 UTC 
Created attachment 693642 [details]
File: maps
Comment 11 Louis van Dyk 2013-02-06 02:42:27 UTC 
Created attachment 693643 [details]
File: dso_list
Comment 12 Louis van Dyk 2013-02-06 02:42:30 UTC 
Created attachment 693644 [details]
File: proc_pid_status
Comment 13 Louis van Dyk 2013-02-06 02:42:35 UTC 
Created attachment 693645 [details]
File: var_log_messages
Comment 14 Louis van Dyk 2013-02-06 02:42:38 UTC 
Created attachment 693646 [details]
File: open_fds
Comment 15 Milan Crha 2013-02-06 08:00:01 UTC 
Thanks for a bug report. There is filled a similar upstream bug [1], thus I'm moving this there. Please see [1] for any further updates. If possible, please CC yourself there, in case upstream developers will have additional questions.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=552891