Version-Release number of selected component: mate-file-manager-1.6.1-5.fc19 Additional info: reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: caja -n crash_function: g_type_check_instance_cast executable: /usr/bin/caja kernel: 3.9.4-301.fc19.x86_64 runlevel: N 5 uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 g_type_check_instance_cast at gtype.c:4032 #1 radio_binding_setting_changed at caja-file-management-properties.c:862 #6 g_settings_real_change_event at gsettings.c:288 #7 ffi_call_unix64 at ../src/x86/unix64.S:76 #8 ffi_call at ../src/x86/ffi64.c:522 #9 g_cclosure_marshal_generic_va at gclosure.c:1550 #10 _g_closure_invoke_va at gclosure.c:840 #13 settings_backend_changed at gsettings.c:348 #14 g_settings_backend_invoke_closure at gsettingsbackend.c:271 #19 gtk_main at gtkmain.c:1257
Created attachment 765754 [details] File: backtrace
Created attachment 765755 [details] File: cgroup
Created attachment 765756 [details] File: core_backtrace
Created attachment 765757 [details] File: dso_list
Created attachment 765758 [details] File: environ
Created attachment 765759 [details] File: limits
Created attachment 765760 [details] File: maps
Created attachment 765761 [details] File: open_fds
Created attachment 765762 [details] File: proc_pid_status
Created attachment 765763 [details] File: var_log_messages
Can you describe a little more detailed what's happend? Does this error ocours frequently?
Unfortunately, it happened on my wife's laptop, so I can't really tell what was the reason.
Ok, i can't confirm this on my systems. Hope you agree with me to close this bug, if it happens again post it here and i will re-open the report.