Bug 1028429

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: 19   
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/221b71c2dec30711ec6937d4c7a2fb1ab79d60a1
Whiteboard: abrt_hash:eee46b821978848a134345e3cc97712096c73082
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-08 12:35:59 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: 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-08 12:24:13 UTC 
Description of problem:
On initial startup, after 3.11.7-200.fc19.x86_64

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 (8 frames)
 #2 g_thread_new at gthread.c:839
 #3 g_get_worker_context at gmain.c:5454
 #4 file_is_hidden at glocalfileinfo.c:1510
 #5 _g_local_file_info_get at glocalfileinfo.c:1791
 #6 g_local_file_query_info at glocalfile.c:1228
 #7 query_info_async_thread at gfile.c:5179
 #8 g_task_thread_pool_thread at gtask.c:1242
 #10 g_thread_proxy at gthread.c:798
Comment 1 Nicholas Van Wyen 2013-11-08 12:24:21 UTC 
Created attachment 821576 [details]
File: backtrace
Comment 2 Nicholas Van Wyen 2013-11-08 12:24:24 UTC 
Created attachment 821578 [details]
File: cgroup
Comment 3 Nicholas Van Wyen 2013-11-08 12:24:28 UTC 
Created attachment 821579 [details]
File: core_backtrace
Comment 4 Nicholas Van Wyen 2013-11-08 12:24:31 UTC 
Created attachment 821580 [details]
File: dso_list
Comment 5 Nicholas Van Wyen 2013-11-08 12:24:35 UTC 
Created attachment 821581 [details]
File: environ
Comment 6 Nicholas Van Wyen 2013-11-08 12:24:38 UTC 
Created attachment 821582 [details]
File: limits
Comment 7 Nicholas Van Wyen 2013-11-08 12:24:44 UTC 
Created attachment 821583 [details]
File: maps
Comment 8 Nicholas Van Wyen 2013-11-08 12:24:47 UTC 
Created attachment 821584 [details]
File: open_fds
Comment 9 Nicholas Van Wyen 2013-11-08 12:24:51 UTC 
Created attachment 821585 [details]
File: proc_pid_status
Comment 10 Nicholas Van Wyen 2013-11-08 12:24:54 UTC 
Created attachment 821586 [details]
File: var_log_messages
Comment 11 Nicholas Van Wyen 2013-11-08 12:39:55 UTC 
.
The bug was opened with all information generated, why was it closed with "INSUFFICIENT_DATA". What do you need?

.