Bug 1294636

Summary: [abrt] caja: filesystem_info_stop(): caja killed by SIGABRT
Product: [Fedora] Fedora Reporter: zbechir
Component: cajaAssignee: Wolfgang Ulbrich <fedora>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 23CC: fedora, mithrial
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/50f20e96e6dac463570089116f3ce1ea5bffbe97
Whiteboard: abrt_hash:93ff58dfda4a38d91240d832abe74f8bc1069cc3;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-14 09:41:29 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: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description zbechir 2015-12-29 11:50:16 UTC 
Version-Release number of selected component:
caja-1.12.1-1.fc23

Additional info:
reporter:       libreport-2.6.3
backtrace_rating: 4
cmdline:        caja
crash_function: filesystem_info_stop
executable:     /usr/bin/caja
global_pid:     2917
kernel:         4.2.8-300.fc23.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (7 frames)
 #4 filesystem_info_stop at caja-directory-async.c:4706
 #5 start_or_stop_io at caja-directory-async.c:5028
 #6 caja_directory_async_state_changed at caja-directory-async.c:5110
 #7 caja_directory_notify_files_moved at caja-directory.c:1433
 #8 caja_file_changes_consume_changes at caja-file-changes-queue.c:394
 #9 call_consume_changes_idle_cb at caja-monitor.c:70
 #14 gtk_main at gtkmain.c:1268
Comment 1 zbechir 2015-12-29 11:50:23 UTC 
Created attachment 1110156 [details]
File: backtrace
Comment 2 zbechir 2015-12-29 11:50:25 UTC 
Created attachment 1110157 [details]
File: cgroup
Comment 3 zbechir 2015-12-29 11:50:27 UTC 
Created attachment 1110158 [details]
File: core_backtrace
Comment 4 zbechir 2015-12-29 11:50:29 UTC 
Created attachment 1110159 [details]
File: dso_list
Comment 5 zbechir 2015-12-29 11:50:30 UTC 
Created attachment 1110160 [details]
File: environ
Comment 6 zbechir 2015-12-29 11:50:32 UTC 
Created attachment 1110161 [details]
File: limits
Comment 7 zbechir 2015-12-29 11:50:36 UTC 
Created attachment 1110162 [details]
File: maps
Comment 8 zbechir 2015-12-29 11:50:39 UTC 
Created attachment 1110163 [details]
File: mountinfo
Comment 9 zbechir 2015-12-29 11:50:42 UTC 
Created attachment 1110164 [details]
File: namespaces
Comment 10 zbechir 2015-12-29 11:50:43 UTC 
Created attachment 1110165 [details]
File: open_fds
Comment 11 zbechir 2015-12-29 11:50:45 UTC 
Created attachment 1110166 [details]
File: proc_pid_status
Comment 12 zbechir 2015-12-29 11:50:47 UTC 
Created attachment 1110167 [details]
File: var_log_messages
Comment 13 Wolfgang Ulbrich 2016-01-30 17:48:28 UTC 
Can you provide a valid description?
Steps to reproduce?
Did this issue occurs frequently ?
Is the problem still exists with the latest updates?
Comment 14 Wolfgang Ulbrich 2016-04-14 09:41:29 UTC 
No answer from reporter!