Bug 1342569

Thank you for the report. It would be best if you could run 'reporter-ureport -vvv' in the problem directory (/var/spool/abrt/vmcore...) and attach its output here.

Unfortunately, there isn't (or no longer is) a corresponding directory under /var/spool/abrt/vmcore/. The GUI tool doesn't list any reports either, which is weird since there are directories for other crashes.

Here's what I get if I do this from the only directory I could find -- but I guess that's not useful:
# cd /var/crash/127.0.0.1-2016-06-03-13\:00\:25/
# reporter-ureport -vvv
Configuration file '/etc/libreport/plugins/ureport.conf' contains no option
Unable to open './type': Aucun fichier ou dossier de ce type.

Great, you still have the vmcore at place. Restart abrt-vmcore.service (systemctl restart abrt-vmcore.service) and a new directory in /var/spool/abrt should appear. Please, re-run the command in the new directory.

Cool. Now the directory is here, but I still get the same error:
# cd /var/spool/abrt/vmcore-127.0.0.1-2016-06-03-13\:00\:25/
# reporter-ureport -vvv
Configuration file '/etc/libreport/plugins/ureport.conf' contains no option
Unable to open './pkg_epoch': No such file or directory.

Hmm, can you please run '/usr/libexec/abrt-handle-event -vvv -e post-create .' in that directory. It should either create the missing file or tell us why the missing file does not exist.

Aha, the post-create EVENT does not create the missing file on purpose. The correct command you need to run (and we must add to our scripts) is "abrt-action-analyze-oops && abrt-action-save-package-data".

Created attachment 1165542 [details]
Output of /usr/libexec/abrt-handle-event -vvv -e post-create .

See the attached log. Doesn't seem to make a difference:

# reporter-ureport -vvvConfiguration file '/etc/libreport/plugins/ureport.conf' contains no option
Unable to open './pkg_epoch': No such file or directory
# abrt-action-analyze-oops && abrt-action-save-package-data
Can't open file 'executable': No such file or directory

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.

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.

Created attachment 1314603 [details]
Output of reporter-ureport -vvv

I am also experiencing this problem on Fedora 25. I attached the output of 'reporter-ureport -vvv' as mentioned in the previous comments.

*** This bug has been marked as a duplicate of bug 1481984 ***