Description of problem: I downloaded 2 kindle books from Amazon and moved them (using the caja file manger) to the kindle documents directory as usual. The file manager had 2 windows open, the Downloads folder, and the kindle documents folder. After waiting a minute or so, I ejected the kindle, as usual. At that point the caja file manager crashed. The mount command shows that the kindle is not mounted, and my kindle shows that it is not mounted. Sometimes the file manager issues a notification to wait before unplugging the device, that the device is busy -- I did not see such a notification before the crash. The two books I downloaded are on the kindle and are not corrupted. The user applications that were open at the time of the crash: firefox, evolution, and mate-terminal. Version-Release number of selected component: mate-file-manager-1.5.2-1.fc18 Additional info: backtrace_rating: 4 cmdline: caja crash_function: caja_window_pane_slot_close executable: /usr/bin/caja kernel: 3.7.2-204.fc18.x86_64 uid: 1000 Truncated backtrace: Thread no. 1 (9 frames) #4 caja_window_pane_slot_close at caja-window-pane.c:143 #5 caja_window_slot_close at caja-window.c:994 #6 mount_removed_callback at caja-application.c:1836 #10 g_signal_emit_by_name at gsignal.c:3393 #11 g_cclosure_marshal_VOID__OBJECTv at gmarshal.c:1312 #12 _g_closure_invoke_va at gclosure.c:840 #14 g_signal_emit_by_name at gsignal.c:3393 #15 signal_emit_in_idle_do at gproxyvolumemonitor.c:1052 #20 gtk_main at gtkmain.c:1257
Created attachment 686025 [details] File: backtrace
Created attachment 686026 [details] File: build_ids
Created attachment 686027 [details] File: cgroup
Created attachment 686028 [details] File: core_backtrace
Created attachment 686029 [details] File: dso_list
Created attachment 686030 [details] File: environ
Created attachment 686031 [details] File: limits
Created attachment 686032 [details] File: maps
Created attachment 686033 [details] File: open_fds
Created attachment 686035 [details] File: proc_pid_status
Created attachment 686037 [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).
(In reply to comment #13) > 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). As requested, the updates-testing version was tested, and there was no problem - it worked fine.
Thanks for confirming.
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.