Bug 1030651

Summary: [abrt] mate-file-manager-1.6.3-0.7.gitbf47018.fc19: g_thread_new: Process /usr/bin/caja was killed by signal 5 (SIGTRAP)
Product: [Fedora] Fedora Reporter: Nicholas Van Wyen <nvanwyen>
Component: mate-file-managerAssignee: Dan Mashal <dan.mashal>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: nvanwyen
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/47104d96e6d823a1680ad1838a14ab8a305cc708
Whiteboard: abrt_hash:b6d76e645cb501bd6fe1c24357de57918981752c
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-14 21:12:39 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: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Nicholas Van Wyen 2013-11-14 21:09:59 UTC 
Version-Release number of selected component:
mate-file-manager-1.6.3-0.7.gitbf47018.fc19

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        caja -n
crash_function: g_thread_new
executable:     /usr/bin/caja
kernel:         3.11.7-200.fc19.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 g_thread_new at gthread.c:839
 #3 _g_dbus_shared_thread_ref at gdbusprivate.c:306
 #4 _g_dbus_worker_new at gdbusprivate.c:1680
 #5 initable_init at gdbusconnection.c:2640
 #6 g_bus_get_sync at gdbusconnection.c:6882
 #7 g_daemon_vfs_init at gdaemonvfs.c:297
 #8 g_type_create_instance at gtype.c:1917
 #9 g_object_constructor at gobject.c:1855
 #12 try_implementation at giomodule.c:759
 #13 _g_io_module_get_default at giomodule.c:858
Comment 1 Nicholas Van Wyen 2013-11-14 21:10:06 UTC 
Created attachment 824144 [details]
File: backtrace
Comment 2 Nicholas Van Wyen 2013-11-14 21:10:09 UTC 
Created attachment 824145 [details]
File: cgroup
Comment 3 Nicholas Van Wyen 2013-11-14 21:10:12 UTC 
Created attachment 824146 [details]
File: core_backtrace
Comment 4 Nicholas Van Wyen 2013-11-14 21:10:17 UTC 
Created attachment 824147 [details]
File: dso_list
Comment 5 Nicholas Van Wyen 2013-11-14 21:10:20 UTC 
Created attachment 824148 [details]
File: environ
Comment 6 Nicholas Van Wyen 2013-11-14 21:10:23 UTC 
Created attachment 824149 [details]
File: limits
Comment 7 Nicholas Van Wyen 2013-11-14 21:10:27 UTC 
Created attachment 824150 [details]
File: maps
Comment 8 Nicholas Van Wyen 2013-11-14 21:10:29 UTC 
Created attachment 824151 [details]
File: open_fds
Comment 9 Nicholas Van Wyen 2013-11-14 21:10:32 UTC 
Created attachment 824152 [details]
File: proc_pid_status
Comment 10 Nicholas Van Wyen 2013-11-14 21:10:35 UTC 
Created attachment 824153 [details]
File: var_log_messages
Comment 11 Nicholas Van Wyen 2013-11-14 21:20:03 UTC 
Why does this keep getting closed with INSUFFICIENT_DATA? The attachments backtrace, cgroup, core_backtrace, dso_list, environ, limits, maps, open_fds, proc_pid_status and var_log_messages have been provided ... what else is needed?

Please explain?

Thank you