Hide Forgot
This seems kind of unnecessary. If I download a crash report from openQA - e.g. https://openqa.fedoraproject.org/tests/35750/file/_graphical_wait_login-spoolabrt.tar.gz - and just extract it in /tmp or something , I cannot report it with abrt-cli . I cannot report it even if I change the directory's ownership to abrt.abrt and set SELinux to permissive - it just continues to do this: [root@adam tmp]# abrt-cli report /tmp/ccpp-2016-09-23-09\:58\:30-1525 Can't test whether the element exists over abrt-dbus: GDBus.Error:org.freedesktop.problems.InvalidProblemDir: '/tmp/ccpp-2016-09-23-09:58:30-1525' is not a valid problem directory Problem '/tmp/ccpp-2016-09-23-09:58:30-1525' cannot be reported it only works if I move it to /var/spool/abrt: [root@adam tmp]# mv ccpp-2016-09-23-09\:58\:30-1525/ /var/spool/abrt [root@adam tmp]# abrt-cli report /var/spool/abrt/ccpp-2016-09-23-09\:58\:30-1525 ('report_uReport' completed successfully) ... this is rather inconvenient and, if I don't remember to clean up afterwards, means I don't know when I run abrt-cli which crashes actually happened to me and which are ones I downloaded for reporting from openQA. abrt-cli also refuses to accept problem directories with a trailing / and prints a misleading error, which I reported months ago but never got fixed...
I agree that this behavior is extremely odd and we will try to fix it ASAP. It roots from the fact that abrt-cli access /var/spool/abrt directorires in-directly though abrt-dbus. Until this bug is fixed, you can use the 'report-cli' utility to report random directories.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 '25'. 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 25 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.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.