Version-Release number of selected component: mate-file-manager-1.6.3-0.7.gitbf47018.fc19 Additional info: reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: caja -n crash_function: caja_window_slot_info_get_current_location executable: /usr/bin/caja kernel: 3.11.7-200.fc19.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #4 caja_window_slot_info_get_current_location at caja-window-slot-info.c:141 #5 update_places at caja-places-sidebar.c:488 #9 g_signal_emit_by_name at gsignal.c:3424 #10 g_cclosure_marshal_VOID__OBJECTv at gmarshal.c:1312 #11 _g_closure_invoke_va at gclosure.c:840 #13 g_signal_emit_by_name at gsignal.c:3424 #14 mount_removed at gdaemonvolumemonitor.c:191 #15 g_cclosure_marshal_VOID__POINTERv at gmarshal.c:1236 #16 _g_closure_invoke_va at gclosure.c:840 #19 g_mount_tracker_remove_mount at gmounttracker.c:414 Potential duplicate: bug 920359
Created attachment 824547 [details] File: backtrace
Created attachment 824548 [details] File: cgroup
Created attachment 824549 [details] File: core_backtrace
Created attachment 824550 [details] File: dso_list
Created attachment 824551 [details] File: environ
Created attachment 824552 [details] File: limits
Created attachment 824553 [details] File: maps
Created attachment 824554 [details] File: open_fds
Created attachment 824555 [details] File: proc_pid_status
Created attachment 824556 [details] File: var_log_messages
He, i'm very happy if you notice me about a caja issue and it was not the fist time that you open a report. But why you can't write more info's like what you did, or if that ocours everytime, is it reproduceable? You don't need to write a book ;) Sorry without those infos a bugreport is complete useless, because i can't reproduce it and upstream don't work on bugs without user interaction.
Hi, sorry for not describing problem at the moment. I'm not sure in problem cause, because caja was in background for dozens of minutes when crashes. There are two ssh folders mounted via "Connect to server..." was opened at caja. One ssh folder from virtual box whith centos linux on my machine, and other ssh folder from remote machine with rhel. Most possible that remote machine was rebooted and it was cause of crash.
update: rebooted or disconnected from network.
forward to upstream. https://github.com/mate-desktop/caja/issues/201
Upstream couldn't reproduce the issue and closed upstream report, I will follow, feel free to report here if this issue still exists.