I’ve had some very important reports deleted because it didn’t consider them to be useful:
Regardless of how they appear in gnome-abrt’s GUI, can I have abrt retain all reports? I do like that it clears duplicates, but I’d much rather just have a report marked as a duplicate of another, than have it removed! [1] I’ve TiBs free.
MaxCrashReportsSize = number
The maximum disk space (specified in MiB) that ABRT will use for all the crash dumps. Value of 0 means "unlimited space".
Default is 5000.
@glb, I didn’t know that one could man a filename, as if it were in $PATH! Thanks!
I’ve set /etc/abrt/abrt.conf to:
# Configuration for the ABRT daemon
# ---------------------------------
#
# This config file is empty by default which means that the preconfigured
# default values will be used by ABRT. If you wish to override the default
# settings, you can do so here.
#
# For details regarding the contents of this file and the defaults, see
# `man 5 abrt.conf`.
MaxCrashReportsSize=0
…since I presume that it utilises either .desktop or .sh syntax.
I don’t see any options to prevent it deleting reports that it doesn’t consider to be useful, however.
Just for the record, one of the first things I often do when I want to investigate a program’s settings and capabilities is run rpm -ql <package-name>. In this case, I was looking for what config files existed. Sometimes there are config files under /usr that determine defaults. In this case, it showed that there was a man page for abrt.conf.
As a temporary workaround, deleting the problem in gnome-abrt (abrt remove isn’t sufficient), [1] then reproducing it, appears to remediate this, [2] thereby allowing me to bypass t/132081/27. [3][4]
RokeJulianLockhart@Beedell:~$ abrt list
Id 876eb19
Component chromium
Count 3
Time 2025-08-28 12:51:32
User id 1000 (RokeJulianLockhart)
Reported to
ABRT Server https://retrace.fedoraproject.org/faf/reports/bthash/06955e65649a3880dc66f61a7767a685d8e154fd
RokeJulianLockhart@Beedell:~$ abrt remove 876eb19
Id 876eb19
Component chromium
Count 3
Time 2025-08-28 12:51:32
Command line $'/usr/lib64/chromium-browser/chromium-browser --type=gpu-process --enable-gpu-rasterization --enable-native-gpu-memory-buffers --use-angle=gl --crashpad-handler-pid=7838 --enable-crash-reporter=,Fedora Project --disable-breakpad --change-stack-guard-on-fork=enable --gpu-preferences=UAAAAAAAAAAgAAAYAAAAAAAAAAAAAGAAAQAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAYAAAAAAAAABgAAAAAAAAAAQAAAAAAAAAIAAAAAAAAAAgAAAAAAAAA --use-gl=angle --shared-files --metrics-shmem-handle=4,i,5956773514937297173,3597146344334645978,262144 --field-trial-handle=3,i,14338598026711943823,14963882441025114410,262144 --enable-features=AcceleratedVideoDecodeLinuxGL,AcceleratedVideoEncoder --disable-features=EyeDropper --variations-seed-version'
Package chromium-139.0.7258.138-1.fc42
User id 1000 (RokeJulianLockhart)
Path /var/spool/abrt/ccpp-2025-08-28-12:51:32.136516-7877
Reported to
ABRT Server https://retrace.fedoraproject.org/faf/reports/bthash/06955e65649a3880dc66f61a7767a685d8e154fd
Are you sure you want to delete this problem? [y/N] y
Removed
Id 926d49e
Component chromium
Count 1
Time 2025-10-22 22:24:34
User id 1000 (RokeJulianLockhart)
RokeJulianLockhart@Beedell:~$ abrt report 926d49e
Reporting problem 926d49e
no actions matching this problem found for event 'collect_GConf'
no actions matching this problem found for event 'collect_vimrc_system'
no actions matching this problem found for event 'collect_vimrc_user'
no actions matching this problem found for event 'collect_xsession_errors'
('report_uReport' completed successfully)
Generating backtrace
Backtrace is generated and saved, 163312 bytes
Looking for similar problems in bugzilla
Bugzilla API key: $key
No changes were detected in the report
Checking for duplicates
Creating a new bug...
Adding External URL to bug 2405937
Adding attachments to bug 2405937
Status: NEW https://bugzilla.redhat.com/show_bug.cgi?id=2405937
('post_report' completed successfully)
Id 2edadf7
Component chromium
Count 2
Time 2025-10-18 12:23:38
User id 1000 (RokeJulianLockhart)
Reported to
ABRT Server https://retrace.fedoraproject.org/faf/reports/bthash/6223aaeeb54d9a2aeac4a0ff0af1afde40cb2818
RokeJulianLockhart@Beedell:~$ abrt report 2edadf7
Reporting problem 2edadf7
no actions matching this problem found for event 'collect_GConf'
no actions matching this problem found for event 'collect_vimrc_system'
no actions matching this problem found for event 'collect_vimrc_user'
no actions matching this problem found for event 'collect_xsession_errors'
('report_uReport' completed successfully)
Generating backtrace
Backtrace is generated and saved, 61793 bytes
Looking for similar problems in bugzilla
Reporting is disabled because the generated backtrace has low informational value.
Please try to install debuginfo manually using the command: "dnf debuginfo-install chromium-141.0.7390.76-1.fc42" and try again.