Bug 1122303

Summary: [abrt] mate-file-manager: __pthread_cond_timedwait(): caja killed by SIGTRAP
Product: [Fedora] Fedora Reporter: Al Dunsmuir <al.dunsmuir>
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: 20CC: al.dunsmuir, dan.mashal, raveit65.sun, rdieter, stefano
Target Milestone: ---   
Target Release: ---   
Hardware: ppc64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/b496ea12c9b39eb96689d8fd784984e58f7a7244
Whiteboard: abrt_hash:5de2da6640fa86ca120fa50127a1e150a3eaa0a1
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-23 08:22:27 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: 2271.txt
none
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 Al Dunsmuir 2014-07-22 21:44:59 UTC 
Description of problem:
Manually reported this problem using gdb-generated backtrace.
See https://bugzilla.redhat.com/show_bug.cgi?id=1121724

Version-Release number of selected component:
mate-file-manager-1.6.4-4.fc20

Additional info:
reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        caja
crash_function: __pthread_cond_timedwait
executable:     /usr/bin/caja
kernel:         3.14.5-200.fc20.ppc64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 5 (5 frames)
 #0 __pthread_cond_timedwait at pthread_cond_timedwait.c:199
 #1 g_cond_wait_until at gthread-posix.c:870
 #2 g_async_queue_pop_intern_unlocked at gasyncqueue.c:424
 #3 g_thread_pool_wait_for_new_task at gthreadpool.c:264
 #5 g_thread_proxy at gthread.c:798
Comment 1 Al Dunsmuir 2014-07-22 21:45:02 UTC 
Created attachment 920050 [details]
File: 2271.txt
Comment 2 Al Dunsmuir 2014-07-22 21:45:03 UTC 
Created attachment 920051 [details]
File: backtrace
Comment 3 Al Dunsmuir 2014-07-22 21:45:04 UTC 
Created attachment 920052 [details]
File: cgroup
Comment 4 Al Dunsmuir 2014-07-22 21:45:05 UTC 
Created attachment 920053 [details]
File: core_backtrace
Comment 5 Al Dunsmuir 2014-07-22 21:45:06 UTC 
Created attachment 920054 [details]
File: dso_list
Comment 6 Al Dunsmuir 2014-07-22 21:45:07 UTC 
Created attachment 920055 [details]
File: environ
Comment 7 Al Dunsmuir 2014-07-22 21:45:08 UTC 
Created attachment 920056 [details]
File: limits
Comment 8 Al Dunsmuir 2014-07-22 21:45:09 UTC 
Created attachment 920057 [details]
File: maps
Comment 9 Al Dunsmuir 2014-07-22 21:45:10 UTC 
Created attachment 920058 [details]
File: open_fds
Comment 10 Al Dunsmuir 2014-07-22 21:45:11 UTC 
Created attachment 920059 [details]
File: proc_pid_status
Comment 11 Al Dunsmuir 2014-07-22 21:45:12 UTC 
Created attachment 920060 [details]
File: var_log_messages
Comment 12 Wolfgang Ulbrich 2014-10-04 14:44:47 UTC 
Does this issue still exists with caja-1.8.x ?