Bug 902513

Summary: [abrt] evolution-3.4.4-2.fc17: gtk_tree_path_new_from_node: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Adam Stein <adam>
Component: gtk3Assignee: Matthias Clasen <mclasen>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: lucilanga, mbarnes, mclasen, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:d815ab0b59461b7f916dbbd566228f539dfc770a
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-01 04:40:23 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: var_log_messages
none
File: core_backtrace
none
File: environ
none
File: limits
none
File: backtrace
none
File: cgroup
none
File: gconf_subtree
none
File: smolt_data
none
File: xsession_errors
none
File: executable
none
File: maps
none
File: dso_list
none
File: proc_pid_status
none
File: build_ids
none
File: open_fds none

Description Adam Stein 2013-01-21 20:29:04 UTC 
Description of problem:
Had started the "import a file" process.  Had one of the dialog windows up for the import process and Evolution just crashed.  This was AFTER importing a file.

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:        /usr/bin/evolution
crash_function: gtk_tree_path_new_from_node
kernel:         3.6.11-5.fc17.x86_64

truncated backtrace:
:Thread no. 1 (10 frames)
: #4 gtk_tree_path_new_from_node at gtkfilesystemmodel.c:269
: #6 gtk_cell_area_real_apply_attributes at gtkcellarea.c:1317
: #7 gtk_cell_area_box_apply_attributes at gtkcellareabox.c:1317
: #8 _gtk_marshal_VOID__OBJECT_BOXED_BOOLEAN_BOOLEANv at gtkmarshalers.c:4874
: #9 _g_closure_invoke_va at gclosure.c:840
: #12 gtk_cell_area_apply_attributes at gtkcellarea.c:2362
: #13 gtk_tree_view_column_cell_set_cell_data at gtktreeviewcolumn.c:2872
: #14 gtk_tree_view_bin_draw at gtktreeview.c:4865
: #15 gtk_tree_view_draw at gtktreeview.c:5365
: #16 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:85
Comment 1 Adam Stein 2013-01-21 20:29:06 UTC 
Created attachment 684619 [details]
File: var_log_messages
Comment 2 Adam Stein 2013-01-21 20:29:08 UTC 
Created attachment 684620 [details]
File: core_backtrace
Comment 3 Adam Stein 2013-01-21 20:29:10 UTC 
Created attachment 684621 [details]
File: environ
Comment 4 Adam Stein 2013-01-21 20:29:11 UTC 
Created attachment 684622 [details]
File: limits
Comment 5 Adam Stein 2013-01-21 20:29:13 UTC 
Created attachment 684623 [details]
File: backtrace
Comment 6 Adam Stein 2013-01-21 20:29:15 UTC 
Created attachment 684624 [details]
File: cgroup
Comment 7 Adam Stein 2013-01-21 20:29:16 UTC 
Created attachment 684625 [details]
File: gconf_subtree
Comment 8 Adam Stein 2013-01-21 20:29:18 UTC 
Created attachment 684626 [details]
File: smolt_data
Comment 9 Adam Stein 2013-01-21 20:29:20 UTC 
Created attachment 684627 [details]
File: xsession_errors
Comment 10 Adam Stein 2013-01-21 20:29:22 UTC 
Created attachment 684628 [details]
File: executable
Comment 11 Adam Stein 2013-01-21 20:29:24 UTC 
Created attachment 684629 [details]
File: maps
Comment 12 Adam Stein 2013-01-21 20:29:25 UTC 
Created attachment 684630 [details]
File: dso_list
Comment 13 Adam Stein 2013-01-21 20:29:27 UTC 
Created attachment 684631 [details]
File: proc_pid_status
Comment 14 Adam Stein 2013-01-21 20:29:29 UTC 
Created attachment 684632 [details]
File: build_ids
Comment 15 Adam Stein 2013-01-21 20:29:31 UTC 
Created attachment 684633 [details]
File: open_fds
Comment 16 Milan Crha 2013-01-22 16:27:35 UTC 
Thanks for a bug report. I see in the backtrace that all the threads are basically idle, except of the main thread, which is in a gtk's idle handler. The crash may or may not be caused by evolution itself, only the crashing thread has just the main() function in it from evolution, all the rest is gtk+ or glib2, thus I'm moving this to gtk+ for further investigation.
Comment 17 Adam Stein 2013-01-22 16:57:07 UTC 
Thanks for taking a look.  Hopefully enough information was saved to indicate what might have happened.  I don't remember exactly what else might have been running at the time.
Comment 18 Fedora End Of Life 2013-07-04 00:42:27 UTC 
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 19 Fedora End Of Life 2013-08-01 04:40:27 UTC 
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.