Update in F18, amongst others abrt-2.1.7-1.fc18 -> 2.1.9-1.fc18, during the cleanup state, spitted lines like this: > chown: cannot access ?/var/tmp/abrt/ccpp-2013-05-22-17:17:01-212/*?: No such file or directory > chown: cannot access ?/var/tmp/abrt/ccpp-2013-09-30-16:19:25-25795/*?: No such file or directory > chown: cannot access ?/var/tmp/abrt/pyhook-2013-05-22-17:19:47-2095/*?: No such file or directory > chown: cannot access ?/var/tmp/abrt/ccpp-2013-07-23-23:52:54-9052/*?: No such file or directory > chown: cannot access ?/var/tmp/abrt/ccpp-2013-05-23-13:28:04-1874/*?: No such file or directory > chown: cannot access ?/var/tmp/abrt/ccpp-2013-07-16-21:17:13-1617/*?: No such file or directory > chown: cannot access ?/var/tmp/abrt/ccpp-2013-07-20-10:47:38-7040/*?: No such file or directory > chown: cannot access ?/var/tmp/abrt/ccpp-2013-09-09-18:13:05-28901/*?: No such file or directory > chown: cannot access ?/var/tmp/abrt/ccpp-2013-07-13-20:30:08-27265/*?: No such file or directory > chown: cannot access ?/var/tmp/abrt/ccpp-2013-09-09-15:35:09-1998/*?: No such file or directory > chown: cannot access ?/var/tmp/abrt/pyhook-2013-08-02-23:01:00-25290/*?: No such file or directory > chown: cannot access ?/var/tmp/abrt/pyhook-2013-03-28-18:13:05-1386/*?: No such file or directory > chown: cannot access ?/var/tmp/abrt/ccpp-2013-08-01-19:17:17-13966/*?: No such file or directory > chown: cannot access ?/var/tmp/abrt/pyhook-2013-07-20-16:11:56-22167/*?: No such file or directory > chown: cannot access ?/var/tmp/abrt/ccpp-2013-07-19-18:47:25-13746/*?: No such file or directory > chown: cannot access ?/var/tmp/abrt/pyhook-2013-09-18-18:58:38-26807/*?: No such file or directory > chown: cannot access ?/var/tmp/abrt/pyhook-2013-07-20-16:36:16-24920/*?: No such file or directory > chown: cannot access ?/var/tmp/abrt/pyhook-2013-08-02-20:29:14-30414/*?: No such file or directory > chown: cannot access ?/var/tmp/abrt/ccpp-2013-06-11-15:47:06-26843/*?: No such file or directory > chown: cannot access ?/var/tmp/abrt/pyhook-2013-08-01-22:02:05-5113/*?: No such file or directory > chown: cannot access ?/var/tmp/abrt/ccpp-2013-05-25-02:15:06-3561/*?: No such file or directory > chown: cannot access ?/var/tmp/abrt/ccpp-2013-06-06-16:02:33-9998/*?: No such file or directory and then followed a time gap of about 4 minutes. Using the meantime to look of what is going on, following scriptlet was run: > service abrt-ccpp condrestart >/dev/null 2>&1 || : > # Regenerate core_bactraces because of missing crash threads > abrtdir=$(grep "DumpLocation" /etc/abrt/abrt.conf | cut -d'=' -f2 | tr -d ' ') > if test -d "$abrtdir"; then > for DD in `find "$abrtdir" -mindepth 1 -maxdepth 1 -type d` > do > if test -f "$DD/analyzer" && grep -q "^CCpp$" "$DD/analyzer"; then > /usr/bin/abrt-action-generate-core-backtrace -d "$DD" -- >/dev/null 2>&1 || : > test -f "$DD/core_backtrace" && chown `stat --format=%U:abrt $DD` "$DD/core_backtrace" || : > fi > done > fi and stracing the current child process: > brk(0x7f3fa8b60000) = 0x7f3fa8b60000 > brk(0) = 0x7f3fa8b60000 > brk(0x7f3fa8c38000) = 0x7f3fa8c38000 > brk(0) = 0x7f3fa8c38000 > brk(0x7f3fa8d15000) = 0x7f3fa8d15000 > brk(0) = 0x7f3fa8d15000 > brk(0x7f3fa8def000) = 0x7f3fa8def000 > brk(0) = 0x7f3fa8def000 > brk(0) = 0x7f3fa8def000 and so on and so forth. Would be nice if some informative message of what is going on was provided along those chown errors. The other question if this regenerating was really necessary, I could not find any related bug that would complain about it; the only hint was: > * Wed Sep 11 2013 Jakub Filak <jfilak> 2.1.7-1 > [...] > - abrt-handle-event: add check for missing crash thread
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.