Created attachment 1477890 [details] Screenshot Description of problem: The system informed me a kernel error occurred and could not be reported automatically and suggested that I contact the kernel maintainers manually. Version-Release number of selected component (if applicable): 4.17.14 How reproducible: Happened once. Steps to Reproduce: 1. Wake up 2. Drink coffee 3. Use computer (I was editing a file with vim) Actual results: The kernel reported an error. Expected results: The kernel doesn't report an error. Additional info: See screenshot. That's all the information I have. The data directory referenced in the screenshot no longer exists.
If the data referenced is not available there's not really a lot of reason to keep this bug open because we can't debug it. I'm also not sure why it was lableed as kernel since the error seems to be a segfault in chrome. I'm going to move this to the abrt team to see if we can figure out why this is being flagged as kernel.
(In reply to Laura Abbott from comment #1) > I'm also not sure why it was lableed as kernel since the error seems to be > to be a segfault in chrome. I'm going to move this to the abrt team to see > if we can figure out why this is being flagged as kernel. ABRT watches a systemd-journal for suspicious strings[1] in order to detect kernel oopses[2] and one of the suspicious strings happends to be "invalid opcode"[3]. [1] https://github.com/abrt/abrt/blob/ba1aeaf03a366afd6903aa4a21cd97ec2f27cefe/src/lib/kernel.c#L84 [2] https://abrt.readthedocs.io/en/latest/design.html#oops-watcher [3] https://wiki.osdev.org/Exceptions#Invalid_Opcode
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.