Created attachment 1306364 [details] log extract of abrt looping around I recently had some laptop trouble which I had to hard-reboot from. This caused some disk corruption. When I got back after a restart, abrt started going crazy (see attachment). I ended up having to wipe my journal (rm -rf /var/log/journal), restart systemd-journald, and abrt-everything to get things quiet again. Unfortunately, I don't have a copy for post-mortem purposes; I didn't think of that until *after* I was trying to stop it from reporting a few hundred crashes a minute. My guess is that something did actually crash (which subsequently caused me to have to hard-reboot); this was logged in the journal in a corrupted form, and abrt (or some other piece of the puzzle) didn't manage to cope with that situation. Note that the line: Jul 29 21:00:28 adele abrt-dump-journal-oops[930]: abrt-dump-journal-oops: Found oopses: 6 ... was repeated, always with the same 6 oopses count, further leading me to believe that something got "stuck". Setting severity to high, because although I doubt this sort of situation occurs often, it's very difficult to recover from when it does happen.
Note that I do still a bunch (422 to be exact) of repeated crash reports in the UI. If those would be of use somehow, I can provide them.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. 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 '26'. 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 26 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 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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.