Bug 1142057

Summary: [abrt] caja: g_type_check_instance_is_a(): caja killed by SIGSEGV
Product: [Fedora] Fedora Reporter: ssabchew <ssabcew>
Component: cajaAssignee: Wolfgang Ulbrich <raveit65.sun>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: dan.mashal, raveit65.sun
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/e6964ce95fbd13def3ea3ccf79a4d75bb928656a
Whiteboard: abrt_hash:9b53a8e6c8ff399b9a77680284e577a82bb488d0
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-11-13 13:43:43 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
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 ssabchew 2014-09-16 06:01:57 UTC 
Version-Release number of selected component:
caja-1.8.1-5.fc20

Additional info:
reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        caja --no-desktop computer:///
crash_function: g_type_check_instance_is_a
executable:     /usr/bin/caja
kernel:         3.15.10-201.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 gtk_widget_destroy at gtkwidget.c:3187
 #2 connect_dialog_restore_info_bar at caja-connect-server-dialog.c:159
 #3 connect_dialog_set_info_bar_error at caja-connect-server-dialog.c:284
 #4 mount_enclosing_ready_cb at caja-connect-server-dialog.c:495
 #5 g_simple_async_result_complete at gsimpleasyncresult.c:777
 #6 mount_reply at gdaemonfile.c:2004
 #7 g_simple_async_result_complete at gsimpleasyncresult.c:777
 #8 reply_cb at gdbusproxy.c:2630
 #9 g_simple_async_result_complete at gsimpleasyncresult.c:777
Comment 1 ssabchew 2014-09-16 06:02:07 UTC 
Created attachment 937798 [details]
File: backtrace
Comment 2 ssabchew 2014-09-16 06:02:10 UTC 
Created attachment 937799 [details]
File: cgroup
Comment 3 ssabchew 2014-09-16 06:02:18 UTC 
Created attachment 937800 [details]
File: core_backtrace
Comment 4 ssabchew 2014-09-16 06:02:21 UTC 
Created attachment 937801 [details]
File: dso_list
Comment 5 ssabchew 2014-09-16 06:02:24 UTC 
Created attachment 937802 [details]
File: environ
Comment 6 ssabchew 2014-09-16 06:02:27 UTC 
Created attachment 937803 [details]
File: exploitable
Comment 7 ssabchew 2014-09-16 06:02:29 UTC 
Created attachment 937804 [details]
File: limits
Comment 8 ssabchew 2014-09-16 06:02:36 UTC 
Created attachment 937805 [details]
File: maps
Comment 9 ssabchew 2014-09-16 06:02:39 UTC 
Created attachment 937806 [details]
File: open_fds
Comment 10 ssabchew 2014-09-16 06:02:42 UTC 
Created attachment 937807 [details]
File: proc_pid_status
Comment 11 ssabchew 2014-09-16 06:02:46 UTC 
Created attachment 937808 [details]
File: var_log_messages
Comment 12 Wolfgang Ulbrich 2014-10-23 17:18:32 UTC 
Can you describe a little more detailed what happend?
Did this issue occurs frequently ?
Comment 13 Wolfgang Ulbrich 2014-11-13 13:43:43 UTC 
no answer from reporter