Version-Release number of selected component: caja-1.8.1-5.fc20 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: caja --sm-client-id 234ac241e-1e78-4183-95f2-659277059380 crash_function: caja_window_get_active_slot executable: /usr/bin/caja kernel: 3.15.10-201.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (8 frames) #0 caja_window_get_active_slot at caja-window.c:2064 #1 update_places at caja-places-sidebar.c:487 #5 g_signal_emit_by_name at gsignal.c:3426 #6 g_cclosure_marshal_VOID__OBJECTv at gmarshal.c:1312 #7 _g_closure_invoke_va at gclosure.c:840 #9 g_signal_emit_by_name at gsignal.c:3426 #10 signal_emit_in_idle_do at gproxyvolumemonitor.c:1051 #15 gtk_main at gtkmain.c:1257
Created attachment 934666 [details] File: backtrace
Created attachment 934668 [details] File: cgroup
Created attachment 934669 [details] File: core_backtrace
Created attachment 934670 [details] File: dso_list
Created attachment 934671 [details] File: environ
Created attachment 934672 [details] File: limits
Created attachment 934673 [details] File: maps
Created attachment 934674 [details] File: open_fds
Created attachment 934675 [details] File: proc_pid_status
Created attachment 934676 [details] File: var_log_messages
Created attachment 934677 [details] File: exploitable
Can you describe a little more detailed what happend? Did this issue occurs frequently ?
I don't know. But it happened once, if I remember.