Description of problem: I have no idea how the problem happened as ABRT didn't run until later so I don't recall what I did. Version-Release number of selected component: libreoffice-core-4.1.5.3-1.fc19 Additional info: reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: /usr/lib64/libreoffice/program/soffice.bin '1923 Replace Xythos Project Charter.docx' 'b1923 Replace Xythos Project Charter.docx' --splash-pipe=5 crash_function: gtk_file_system_model_sort.part.0 executable: /usr/lib64/libreoffice/program/soffice.bin kernel: 3.13.5-103.fc19.x86_64 runlevel: N 5 type: CCpp uid: 1000 var_log_messages: Mar 19 17:19:39 kite abrt-hook-ccpp[23774]: Saved core dump of pid 18813 (/usr/lib64/libreoffice/program/soffice.bin) to /var/tmp/abrt/ccpp-2014-03-19-17:19:37-18813 (184311808 bytes) Truncated backtrace: Thread no. 1 (10 frames) #4 gtk_file_system_model_sort.part.0 at /lib64/libgtk-x11-2.0.so.0 #5 _gtk_file_system_model_update_file at /lib64/libgtk-x11-2.0.so.0 #6 gtk_file_system_model_query_done at /lib64/libgtk-x11-2.0.so.0 #7 g_task_return_now at /lib64/libgio-2.0.so.0 #8 complete_in_idle_cb at /lib64/libgio-2.0.so.0 #10 g_main_context_iterate.isra.22 at /lib64/libglib-2.0.so.0 #11 g_main_context_iteration at /lib64/libglib-2.0.so.0 #12 GtkData::Yield(bool, bool) at /usr/lib64/libreoffice/program/libvclplug_gtklo.so #13 Application::Yield(bool) at /usr/lib64/libreoffice/program/libvcllo.so #14 Application::Execute() at /usr/lib64/libreoffice/program/libvcllo.so
Created attachment 876654 [details] File: backtrace
Created attachment 876655 [details] File: cgroup
Created attachment 876656 [details] File: core_backtrace
Created attachment 876657 [details] File: dso_list
Created attachment 876658 [details] File: environ
Created attachment 876659 [details] File: limits
Created attachment 876660 [details] File: maps
Created attachment 876661 [details] File: open_fds
Created attachment 876662 [details] File: proc_pid_status
Yeah, there is this intermittent crash in gtk itself which is going on for some years now, tricky to track down I presume *** This bug has been marked as a duplicate of bug 1032102 ***