ABRT-AUTO-REPORTIN(1)

📦
version 2.17.9 · 3 versions
, in fedora 43, fedora 44

✨ ABRT-AUTO-REPORTIN(1) ✨

abrt-auto-reporting 💖 ABRT Manual

Okay bestie, this is the page for abrt-auto-reporting 🦋 It's how you check or change the auto reporting option values. Literally the settings page for "should my crashes get sent off automatically," and I'm obsessed. 💅

📜 NAME

abrt-auto-reporting — Get or modify the auto reporting option values 🌸

🧚 SYNOPSIS

abrt-auto-reporting [-v] [ enabled | yes | 1 | on | disabled | no | 0 |
off ]

💕 DESCRIPTION

So the tool reads your configuration from abrt.conf and saves any changes back to that same file. No drama. 🫶

The changes take effect immediately, so you don't have to restart any ABRT process. And they're persistent, meaning they stick around. Iconic. ✨

Here are the two vibes you can pick from:

  • disabled — you have to report detected problems manually. You're in full control, bestie. 🎀
  • enabled — ABRT uploads a uReport for a detected problem right after the detection phase. Automatic, no cap. 🔥

🦋 uReport description

Okay so ABRT supports uReports for four types of crashes: 💀

  • crashes of C/C++ programs that result in a core dump
  • uncaught Python exceptions
  • uncaught Java exceptions
  • kernel oopses

Each uReport usually has a stack trace, or multiple stack traces if it's a multi-threaded C/C++ or Java program. The stack trace only shows the call stack of the program at the moment it crashed. It does not include the contents of any variables, so your secrets are safe. 🙈

Every uReport also includes the identification of the operating system, the versions of the RPM packages involved in the crash, and whether the program ran under a root user. The main character details. 👑

There are also extra items for each crash type:

  • C/C++ crashes: the path to the executable and the signal delivered to the program.
  • Python exceptions: the type of the exception, but not the error message, because that might have sensitive data in it. 🫣
  • Kernel oopses: the list of loaded kernel modules, the list of taint flags, and the full text of the kernel oops. 🌈
⚠️ Warning: The full text of a kernel oops might contain information like the identification of the host hardware type. If you don't want to share that with Red Hat, you should disable the autoreporting feature. Protect your vibe! 💜

🎀 OPTIONS

  • -v, --verbose — Be more verbose. You can give it multiple times if you want extra chatty. 🗣️

🔗 SEE ALSO

abrt.conf(5) 🍓

👯 AUTHORS

  • ABRT team 🌟

Shoutout to abrt 2.17.9, last updated 08/03/2026, for keeping the crash reports slay. Stay iconic, bestie! 💖🦋✨

📦 where this page comes from