The original bug is still present. +++ This bug was initially created as a clone of Bug #1120859 +++ Description of problem: ABRT regularly deletes old problem reports, presumably to save space on the user's hard drive. But these reports disappear from gnome-abrt's problem list mysteriously, without any explaination to the user. They either should remain in the list forever, with disabled functionality (ideal), or else there should be a notice in the UI to explain why old reports often disappear. Version-Release number of selected component: gnome-abrt-0.3.7 Additional info: reporter: libreport-2.2.2 kernel: 3.15.4-200.fc20.x86_64 type: libreport --- Additional comment from Christian Stadelmann on 2016-04-11 05:52:20 EDT --- I've never seen abrt/libreport doing that, and I have dozends of bug reports. Can you confirm this issue is happening? Maybe you are just mistaking this for the fact that abrt is auto-detecting duplicate crashes and changes the date in gnome-abrt to the last occurrence. --- Additional comment from Jakub Filak on 2016-04-11 06:04:46 EDT --- (In reply to Christian Stadelmann from comment #3) > I've never seen abrt/libreport doing that, and I have dozends of bug > reports. Can you confirm this issue is happening? > > Maybe you are just mistaking this for the fact that abrt is auto-detecting > duplicate crashes and changes the date in gnome-abrt to the last occurrence. Christian, it is definitely possible. Reproducer: 1. start gnome-abrt 2. # du -sh /var/spool/abrt 3. set MaxCrashReportsSize="the result above - some sane value" in /etc/abrt/abrt.conf 4. generate a new crash (will_segfault) 5. wait until a new entry appears in the list of problems 6. select the new entry and click the Report button 7. close the reporting window 8. several problems dissapear --- Additional comment from Michael Catanzaro on 2016-04-11 08:51:30 EDT --- (In reply to Christian Stadelmann from comment #3) > I've never seen abrt/libreport doing that, and I have dozends of bug > reports. Can you confirm this issue is happening? > > Maybe you are just mistaking this for the fact that abrt is auto-detecting > duplicate crashes and changes the date in gnome-abrt to the last occurrence. It even deletes crashes while they are being reported, which doesn't work too well you can imagine. :) There's a different bug for that somewhere. --- Additional comment from Christian Stadelmann on 2017-11-16 15:00:22 EST --- Still present on F27.
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. 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 '27'. 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 27 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.
This bug appears to have been reported against 'rawhide' during the Fedora 30 development cycle. Changing version to '30.
This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-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 '30'. 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 30 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.
Lately, abrt also started deleting my crashes automatically. I guess this happens roughly since the retrace server is not available any more.
This bug appears to have been reported against 'rawhide' during the Fedora 33 development cycle. Changing version to 33.
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. 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 '33'. 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 33 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 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 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.
This bug appears to have been reported against 'rawhide' during the Fedora 36 development cycle. Changing version to 36.
*** This bug has been marked as a duplicate of bug 1120859 ***