Version-Release number of selected component: gedit-3.8.3-1.fc19 Additional info: reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: gedit crash_function: gtk_tree_row_ref_deleted executable: /usr/bin/gedit kernel: 3.9.9-301.fc19.i686 runlevel: N 5 uid: 1000 xsession_errors: Truncated backtrace: Thread no. 1 (10 frames) #0 gtk_tree_row_ref_deleted at gtktreemodel.c:2094 #1 gtk_tree_row_reference_deleted at gtktreemodel.c:2473 #2 gtk_tree_view_row_deleted at gtktreeview.c:9005 #8 gtk_tree_model_row_deleted at gtktreemodel.c:1867 #9 emit_row_deleted_for_row at gtkfilesystemmodel.c:331 #10 remove_file at gtkfilesystemmodel.c:1912 #11 gtk_file_system_model_monitor_change at gtkfilesystemmodel.c:1257 #12 ffi_call_SYSV at ../src/x86/sysv.S:65 #13 ffi_call at ../src/x86/ffi.c:411 #14 g_cclosure_marshal_generic_va at gclosure.c:1550 Potential duplicate: bug 902427
Created attachment 773546 [details] File: backtrace
Created attachment 773547 [details] File: cgroup
Created attachment 773548 [details] File: core_backtrace
Created attachment 773549 [details] File: dso_list
Created attachment 773550 [details] File: environ
Created attachment 773551 [details] File: limits
Created attachment 773552 [details] File: maps
Created attachment 773553 [details] File: open_fds
Created attachment 773554 [details] File: proc_pid_status
Created attachment 773555 [details] File: var_log_messages
Confirmed here twice.
gtk3-3.14.6-1.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/gtk3-3.14.6-1.fc21
Package gtk3-3.14.6-1.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing gtk3-3.14.6-1.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-16867/gtk3-3.14.6-1.fc21 then log in and leave karma (feedback).
gtk3-3.14.6-1.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.