Version-Release number of selected component: mate-file-manager-1.6.3-1.fc20 Additional info: reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: caja -n crash_function: update_cursor executable: /usr/bin/caja kernel: 3.12.5-302.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 update_cursor at caja-window.c:385 #1 caja_window_sync_allow_stop at caja-window.c:420 #2 caja_window_slot_set_allow_stop at caja-window-slot.c:508 #3 end_location_change at caja-window-manage-views.c:1937 #4 begin_location_change at caja-window-manage-views.c:941 #5 caja_window_slot_open_location_full at caja-window-manage-views.c:690 #6 mount_removed_callback at caja-application.c:1874 #10 g_signal_emit_by_name at gsignal.c:3426 #11 g_cclosure_marshal_VOID__OBJECTv at gmarshal.c:1312 #12 _g_closure_invoke_va at gclosure.c:840
Created attachment 850160 [details] File: backtrace
Created attachment 850161 [details] File: cgroup
Created attachment 850162 [details] File: core_backtrace
Created attachment 850163 [details] File: dso_list
Created attachment 850164 [details] File: environ
Created attachment 850165 [details] File: exploitable
Created attachment 850166 [details] File: limits
Created attachment 850167 [details] File: maps
Created attachment 850168 [details] File: open_fds
Created attachment 850169 [details] File: proc_pid_status
Created attachment 850170 [details] File: var_log_messages
Can you describe a little more detailed what happend? Did this issue occurs frequently ?