ABRT(1)

πŸ“¦
version 2.17.9 Β· 3 versions
, in fedora 43, fedora 44

πŸŽ€ 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