Bug 1304058 - [abrt] caja: directory_count_stop(): caja killed by SIGABRT
Summary: [abrt] caja: directory_count_stop(): caja killed by SIGABRT
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: caja
Version: 23
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Wolfgang Ulbrich
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:5339e8f68987c3dfcbe2f12007a...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-02 18:57 UTC by duartedossantos
Modified: 2016-12-20 18:23 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-20 18:23:32 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (36.64 KB, text/plain)
2016-02-02 18:58 UTC, duartedossantos
no flags Details
File: cgroup (200 bytes, text/plain)
2016-02-02 18:58 UTC, duartedossantos
no flags Details
File: core_backtrace (5.24 KB, text/plain)
2016-02-02 18:58 UTC, duartedossantos
no flags Details
File: dso_list (10.62 KB, text/plain)
2016-02-02 18:58 UTC, duartedossantos
no flags Details
File: environ (1.32 KB, text/plain)
2016-02-02 18:58 UTC, duartedossantos
no flags Details
File: limits (1.29 KB, text/plain)
2016-02-02 18:58 UTC, duartedossantos
no flags Details
File: maps (55.21 KB, text/plain)
2016-02-02 18:58 UTC, duartedossantos
no flags Details
File: mountinfo (4.19 KB, text/plain)
2016-02-02 18:58 UTC, duartedossantos
no flags Details
File: namespaces (85 bytes, text/plain)
2016-02-02 18:58 UTC, duartedossantos
no flags Details
File: open_fds (4.62 KB, text/plain)
2016-02-02 18:58 UTC, duartedossantos
no flags Details
File: proc_pid_status (1.01 KB, text/plain)
2016-02-02 18:58 UTC, duartedossantos
no flags Details
File: var_log_messages (290 bytes, text/plain)
2016-02-02 18:58 UTC, duartedossantos
no flags Details

Description duartedossantos 2016-02-02 18:57:55 UTC
Version-Release number of selected component:
caja-1.12.2-2.fc23

Additional info:
reporter:       libreport-2.6.3
backtrace_rating: 4
cmdline:        caja
crash_function: directory_count_stop
executable:     /usr/bin/caja
global_pid:     1609
kernel:         4.3.3-303.fc23.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #4 directory_count_stop at caja-directory-async.c:2653
 #5 start_or_stop_io at caja-directory-async.c:5020
 #6 caja_directory_async_state_changed at caja-directory-async.c:5110
 #7 call_files_changed_common at caja-directory.c:902
 #8 call_files_changed_free_list at caja-directory.c:912
 #9 g_hash_table_foreach at ghash.c:1607
 #10 caja_directory_notify_files_moved at caja-directory.c:1471
 #11 caja_file_changes_consume_changes at caja-file-changes-queue.c:394
 #12 link_job_done at caja-file-operations.c:5322
 #13 mainloop_proxy_func at gioscheduler.c:200

Comment 1 duartedossantos 2016-02-02 18:58:04 UTC
Created attachment 1120527 [details]
File: backtrace

Comment 2 duartedossantos 2016-02-02 18:58:05 UTC
Created attachment 1120528 [details]
File: cgroup

Comment 3 duartedossantos 2016-02-02 18:58:07 UTC
Created attachment 1120529 [details]
File: core_backtrace

Comment 4 duartedossantos 2016-02-02 18:58:10 UTC
Created attachment 1120530 [details]
File: dso_list

Comment 5 duartedossantos 2016-02-02 18:58:12 UTC
Created attachment 1120531 [details]
File: environ

Comment 6 duartedossantos 2016-02-02 18:58:14 UTC
Created attachment 1120532 [details]
File: limits

Comment 7 duartedossantos 2016-02-02 18:58:20 UTC
Created attachment 1120533 [details]
File: maps

Comment 8 duartedossantos 2016-02-02 18:58:22 UTC
Created attachment 1120534 [details]
File: mountinfo

Comment 9 duartedossantos 2016-02-02 18:58:24 UTC
Created attachment 1120535 [details]
File: namespaces

Comment 10 duartedossantos 2016-02-02 18:58:26 UTC
Created attachment 1120536 [details]
File: open_fds

Comment 11 duartedossantos 2016-02-02 18:58:27 UTC
Created attachment 1120537 [details]
File: proc_pid_status

Comment 12 duartedossantos 2016-02-02 18:58:29 UTC
Created attachment 1120538 [details]
File: var_log_messages

Comment 13 Wolfgang Ulbrich 2016-04-14 09:43:25 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 Fedora End Of Life 2016-11-24 15:21:23 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 15 Fedora End Of Life 2016-12-20 18:23:32 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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