Bug 1034365

Summary: [abrt] mate-file-manager-1.6.3-0.10.gitbf47018.fc20: g_type_check_instance_is_a: Process /usr/bin/caja was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Patrick Monnerat <patrick>
Component: mate-file-managerAssignee: Dan Mashal <dan.mashal>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: dan.mashal, fedora, rdieter, stefano
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/60905b226f02bc267510ad70f716cf695a45d444
Whiteboard: abrt_hash:9c4990db56aceadc543d6f8a424d21e55adbcd79
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-01 09:27:09 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Patrick Monnerat 2013-11-25 16:58:13 UTC 
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
Comment 1 Patrick Monnerat 2013-11-25 16:58:21 UTC 
Created attachment 828759 [details]
File: backtrace
Comment 2 Patrick Monnerat 2013-11-25 16:58:25 UTC 
Created attachment 828760 [details]
File: cgroup
Comment 3 Patrick Monnerat 2013-11-25 16:58:28 UTC 
Created attachment 828761 [details]
File: core_backtrace
Comment 4 Patrick Monnerat 2013-11-25 16:58:32 UTC 
Created attachment 828762 [details]
File: dso_list
Comment 5 Patrick Monnerat 2013-11-25 16:58:35 UTC 
Created attachment 828763 [details]
File: environ
Comment 6 Patrick Monnerat 2013-11-25 16:58:39 UTC 
Created attachment 828764 [details]
File: exploitable
Comment 7 Patrick Monnerat 2013-11-25 16:58:43 UTC 
Created attachment 828765 [details]
File: limits
Comment 8 Patrick Monnerat 2013-11-25 16:58:46 UTC 
Created attachment 828766 [details]
File: maps
Comment 9 Patrick Monnerat 2013-11-25 16:58:50 UTC 
Created attachment 828767 [details]
File: open_fds
Comment 10 Patrick Monnerat 2013-11-25 16:58:53 UTC 
Created attachment 828768 [details]
File: proc_pid_status
Comment 11 Patrick Monnerat 2013-11-25 16:58:57 UTC 
Created attachment 828769 [details]
File: var_log_messages
Comment 12 Wolfgang Ulbrich 2013-11-26 16:28:33 UTC 
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?
Comment 13 Patrick Monnerat 2013-11-26 16:35:10 UTC 
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,
Comment 14 Patrick Monnerat 2013-11-26 16:38:30 UTC 
One more info: the real CPU has 24 cores, 4 assigned to the VM.
We might face a threading problem...
Comment 15 Wolfgang Ulbrich 2013-11-26 18:43:58 UTC 
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.