Bug 1028429 - [abrt] mate-file-manager-1.6.3-0.7.gitbf47018.fc19: g_thread_new: Process /usr/bin/caja was killed by signal 5 (SIGTRAP)
[abrt] mate-file-manager-1.6.3-0.7.gitbf47018.fc19: g_thread_new: Process /us...
Status: CLOSED INSUFFICIENT_DATA
Product: Fedora
Classification: Fedora
Component: mate-file-manager (Show other bugs)
19
x86_64 Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Dan Mashal
Fedora Extras Quality Assurance
https://retrace.fedoraproject.org/faf...
abrt_hash:eee46b821978848a134345e3cc9...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-11-08 07:24 EST by Nicholas Van Wyen
Modified: 2013-11-08 07:39 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-11-08 07:35:59 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
File: backtrace (39.45 KB, text/plain)
2013-11-08 07:24 EST, Nicholas Van Wyen
no flags Details
File: cgroup (141 bytes, text/plain)
2013-11-08 07:24 EST, Nicholas Van Wyen
no flags Details
File: core_backtrace (14.86 KB, text/plain)
2013-11-08 07:24 EST, Nicholas Van Wyen
no flags Details
File: dso_list (7.38 KB, text/plain)
2013-11-08 07:24 EST, Nicholas Van Wyen
no flags Details
File: environ (1.87 KB, text/plain)
2013-11-08 07:24 EST, Nicholas Van Wyen
no flags Details
File: limits (1.29 KB, text/plain)
2013-11-08 07:24 EST, Nicholas Van Wyen
no flags Details
File: maps (36.32 KB, text/plain)
2013-11-08 07:24 EST, Nicholas Van Wyen
no flags Details
File: open_fds (720 bytes, text/plain)
2013-11-08 07:24 EST, Nicholas Van Wyen
no flags Details
File: proc_pid_status (938 bytes, text/plain)
2013-11-08 07:24 EST, Nicholas Van Wyen
no flags Details
File: var_log_messages (18.29 KB, text/plain)
2013-11-08 07:24 EST, Nicholas Van Wyen
no flags Details

  None (edit)
Description Nicholas Van Wyen 2013-11-08 07:24:13 EST
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 07:24:21 EST
Created attachment 821576 [details]
File: backtrace
Comment 2 Nicholas Van Wyen 2013-11-08 07:24:24 EST
Created attachment 821578 [details]
File: cgroup
Comment 3 Nicholas Van Wyen 2013-11-08 07:24:28 EST
Created attachment 821579 [details]
File: core_backtrace
Comment 4 Nicholas Van Wyen 2013-11-08 07:24:31 EST
Created attachment 821580 [details]
File: dso_list
Comment 5 Nicholas Van Wyen 2013-11-08 07:24:35 EST
Created attachment 821581 [details]
File: environ
Comment 6 Nicholas Van Wyen 2013-11-08 07:24:38 EST
Created attachment 821582 [details]
File: limits
Comment 7 Nicholas Van Wyen 2013-11-08 07:24:44 EST
Created attachment 821583 [details]
File: maps
Comment 8 Nicholas Van Wyen 2013-11-08 07:24:47 EST
Created attachment 821584 [details]
File: open_fds
Comment 9 Nicholas Van Wyen 2013-11-08 07:24:51 EST
Created attachment 821585 [details]
File: proc_pid_status
Comment 10 Nicholas Van Wyen 2013-11-08 07:24:54 EST
Created attachment 821586 [details]
File: var_log_messages
Comment 11 Nicholas Van Wyen 2013-11-08 07:39:55 EST
.
The bug was opened with all information generated, why was it closed with "INSUFFICIENT_DATA". What do you need?

.

Note You need to log in before you can comment on or make changes to this bug.