Bug 1572967 - After a kernel panic, the incident reporter creates reports in a loop
Summary: After a kernel panic, the incident reporter creates reports in a loop
Alias: None
Product: Fedora
Classification: Fedora
Component: abrt
Version: 28
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: abrt
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2018-04-29 09:33 UTC by Benjamin Dubois
Modified: 2019-05-28 22:54 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-05-28 22:54:17 UTC
Type: Bug

Attachments (Terms of Use)
first screenshot (182.18 KB, image/png)
2018-04-29 09:33 UTC, Benjamin Dubois
no flags Details
2nd screenshot 1 minute later (150.03 KB, image/png)
2018-04-29 09:34 UTC, Benjamin Dubois
no flags Details

Description Benjamin Dubois 2018-04-29 09:33:34 UTC
Created attachment 1428359 [details]
first screenshot

Description of problem:

After a kernel panic on F28 beta, the crash reporter started sending me notifications that a crash had occurred. the notification comes back every 5 seconds exactly.

I noticed that the incident reporting tool also creates a new (duplicate) report  as fast as it can.

Attached are 2 screenshots showing the number of duplicate incidents created in 1 minute.

Killing abrt-applet resolves the loop

Version-Release number of selected component (if applicable):

How reproducible:


Steps to Reproduce:
1. system crash
2. log in on gnome

Actual results:

an increasing nu;ber of abrt reports and notifications

Expected results:
1 report

Additional info:

initial crash cannot be reported due to proprietary driver

Comment 1 Benjamin Dubois 2018-04-29 09:34:07 UTC
Created attachment 1428360 [details]
2nd screenshot 1 minute later

Comment 2 Stacy Markel 2018-10-15 09:02:04 UTC
Such type of problems arises when we install a new OS. Press ctrl+r to give the command and reinstall your desired OS. For detailed information visit https://www.mactechnicalsupportnumbers.com/apple-id/

Comment 3 Ben Cotton 2019-05-02 20:39:08 UTC
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.

Comment 4 Ben Cotton 2019-05-28 22:54:17 UTC
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

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.