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
Created attachment 920050 [details] File: 2271.txt
Created attachment 920051 [details] File: backtrace
Created attachment 920052 [details] File: cgroup
Created attachment 920053 [details] File: core_backtrace
Created attachment 920054 [details] File: dso_list
Created attachment 920055 [details] File: environ
Created attachment 920056 [details] File: limits
Created attachment 920057 [details] File: maps
Created attachment 920058 [details] File: open_fds
Created attachment 920059 [details] File: proc_pid_status
Created attachment 920060 [details] File: var_log_messages
Does this issue still exists with caja-1.8.x ?