ABRT(1)
π ABRT(1) Β· the ABRT Manual π
okay bestie, this is your guide to ABRT, the tool that keeps track of crashes ("problems") on your machine π It's giving organized, and I'm obsessed. β¨
β¨ NAME β¨
abrt β Manage problems handled by ABRT π
π¦ SYNOPSIS π¦
abrt [OPTIONS...] SUBCOMMAND [MATCH]
Basically you toss in some optional OPTIONS, pick a SUBCOMMAND, and maybe add a MATCH to point at a specific problem π§
πΈ OPTIONS πΈ
-a,--authβ Log in and see every problem on this machine, not just yours π-v,--versionβ Show the program's version number, then bounce π-h,--helpβ Pull up the help message π
π SUBCOMMANDS π
listβ See all the problems ABRT has handled πinfoβ Print the tea on one problem βreportβ Report a problem π£removeβ Delete a problem ποΈbacktraceβ Show the backtrace of a problem π§΅retraceβ Build a backtrace from a coredump πgdbβ Run GDB (the GNU Project debugger) against a problem πdebuginfo-installβ Install the debuginfo packages a problem needs π¦statusβ Check how many recent crashes there have been π
okay so for the detailed list of options for any subcommand, run abrt help SUBCOMMAND π«Ά
π― MATCHING π―
Subcommands that need a single problem, like info or backtrace, will automatically grab the last problem that happened on your system, unless you specify a MATCH π
A MATCH can be a component name, a short hash (you can grab these from the list subcommand), or both together in the form <component>@<hash>. It's giving precision π
π EXAMPLES π
List all problems handled by ABRT π
$ abrt list
List problems with the built-in format β¨
$ abrt list --pretty=oneline
List problems with a custom format π
$ abrt list --fmt '{count}x {short_id} {what}'
Display detailed information about a problem π₯
$ abrt info --pretty full kernel
Run GDB against the last problem π
$ abrt gdb
Generate a backtrace from the last problem's coredump and make a detailed mail report π
$ abrt retrace
$ abrt info --pretty email
π§ FORMATTING π§
Here are the fields you can use for custom formatting, periodt π
{what}β either the component name or the executable π§©{count}β the number of occurrences π’{time}β the time of the last occurrence β°{short_id}β the short hash π{uid}β the user ID π{username}β the username π«Ά{uid_username}β a combo of the two fields above (uid and username) π{path}β the full path to the problem data directory ποΈ{package}β the affected package π¦{cmdline}β the command line used to start an application π
π¦ AUTHORS π¦
- ABRT team π
abrt 2.17.9 Β· 08/03/2026 Β· ABRT(1) π Thanks for reading, bestie, you're literally the best π«Άβ¨
π¦ where this page comes from
- fedora 43: abrt-tui 2.17.9-1.fc43 Β· GPL-2.0-or-later
- fedora 44: abrt-tui 2.17.9-1.fc44 Β· GPL-2.0-or-later
- π girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms