Version-Release number of selected component: brasero-3.10.0-1.fc20 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: brasero crash_function: gtk_tree_row_ref_deleted executable: /usr/bin/brasero kernel: 3.15.10-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 gtk_tree_row_ref_deleted at gtktreemodel.c:2130 #1 gtk_tree_row_reference_deleted at gtktreemodel.c:2509 #2 gtk_tree_view_row_deleted at gtktreeview.c:9057 #7 gtk_tree_model_row_deleted at gtktreemodel.c:1867 #8 emit_row_deleted_for_row at gtkfilesystemmodel.c:331 #9 remove_file at gtkfilesystemmodel.c:1912 #10 gtk_file_system_model_monitor_change at gtkfilesystemmodel.c:1257 #11 ffi_call_unix64 at ../src/x86/unix64.S:76 #12 ffi_call at ../src/x86/ffi64.c:522 #13 g_cclosure_marshal_generic_va at gclosure.c:1550
Created attachment 929932 [details] File: backtrace
Created attachment 929933 [details] File: cgroup
Created attachment 929934 [details] File: core_backtrace
Created attachment 929935 [details] File: dso_list
Created attachment 929936 [details] File: environ
Created attachment 929937 [details] File: exploitable
Created attachment 929938 [details] File: limits
Created attachment 929939 [details] File: maps
Created attachment 929940 [details] File: open_fds
Created attachment 929941 [details] File: proc_pid_status
Created attachment 929942 [details] File: var_log_messages
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.