Hide Forgot
Description of problem: I only clicked the "Computer" icon on the desktop. This is a VM and caja should have show only "VirtIO Disk" and "File System" in a fm window. Subsequent clicks were OK. Version-Release number of selected component: mate-file-manager-1.6.3-0.10.gitbf47018.fc20 Additional info: reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: caja -n crash_function: g_type_check_instance_is_a executable: /usr/bin/caja kernel: 3.11.8-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 g_type_check_instance_is_a at gtype.c:3975 #1 update_node at gtkuimanager.c:2344 #4 do_updates at gtkuimanager.c:2827 #5 gtk_ui_manager_ensure_update at gtkuimanager.c:2882 #6 gtk_ui_manager_real_get_widget at gtkuimanager.c:558 #7 caja_navigation_window_init at caja-navigation-window.c:187 #8 g_type_create_instance at gtype.c:1868 #9 g_object_constructor at gobject.c:2028 #10 caja_window_constructor at caja-window.c:677 #11 g_object_new_with_custom_constructor at gobject.c:1665
Created attachment 828759 [details] File: backtrace
Created attachment 828760 [details] File: cgroup
Created attachment 828761 [details] File: core_backtrace
Created attachment 828762 [details] File: dso_list
Created attachment 828763 [details] File: environ
Created attachment 828764 [details] File: exploitable
Created attachment 828765 [details] File: limits
Created attachment 828766 [details] File: maps
Created attachment 828767 [details] File: open_fds
Created attachment 828768 [details] File: proc_pid_status
Created attachment 828769 [details] File: var_log_messages
Hi Patrick, here in my f20 installations in VM's and on baremetal i can't reproduce the issue. Clicking on "Computer" icon doesn't crash caja. Does this happen every time?
Hi Wolfgang, No, it only crashed once. I reported the abrt bug to provide some material/info to you in case you want to track it, but I have no recipe to reproduce. It occurred on an F20 beta 64bit running in a VM on F18 64bit. It does not block me in any way, so do as you want with the bug report. Cheers,
One more info: the real CPU has 24 cores, 4 assigned to the VM. We might face a threading problem...
My first intention as i read the the backtrace was that it has something to do with the x-caja-window issue, because the backtrace was generated by 'caja -n'. Seems it has something to do with https://bugzilla.redhat.com/show_bug.cgi?id=753882 . But a click on 'Computer' icon opens 'caja --browser'. Anyway, i will the report a while open.