Description of problem: I was browsing a USB drive in Caja, then Caja crashed, appearantly for no reason whatsoever. Version-Release number of selected component: mate-file-manager-1.5.2-1.fc18 Additional info: backtrace_rating: 4 cmdline: caja core_backtrace: crash_function: standard_free executable: /usr/bin/caja kernel: 3.7.8-202.fc18.i686 uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #5 standard_free at gmem.c:98 #7 g_hash_table_remove_all_nodes at ghash.c:536 #8 g_hash_table_remove_all at ghash.c:1345 #9 g_hash_table_destroy at ghash.c:1049 #10 real_destroy at fm-properties-window.c:5582 #17 gtk_object_dispose at gtkobject.c:421 #18 gtk_widget_dispose at gtkwidget.c:8800 #19 gtk_window_dispose at gtkwindow.c:2192 #21 gtk_object_destroy at gtkobject.c:406 #22 gtk_widget_destroy at gtkwidget.c:3189
Created attachment 700646 [details] File: backtrace
Created attachment 700647 [details] File: build_ids
Created attachment 700648 [details] File: cgroup
Created attachment 700649 [details] File: dso_list
Created attachment 700650 [details] File: environ
Created attachment 700651 [details] File: limits
Created attachment 700652 [details] File: maps
Created attachment 700653 [details] File: open_fds
Created attachment 700654 [details] File: proc_pid_status
Created attachment 700655 [details] File: var_log_messages
mate-file-manager-1.5.4-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/mate-file-manager-1.5.4-1.fc18
Package mate-file-manager-1.5.4-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing mate-file-manager-1.5.4-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-3389/mate-file-manager-1.5.4-1.fc18 then log in and leave karma (feedback).
mate-file-manager-1.5.4-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.