REPORT_FEDORA.CONF(5)

💖 report_fedora.conf(5) — the libreport glow-up config 💖

okay bestie, listen. this is the section 5 manual page for report_fedora.conf, the configuration file for libreport. she's small, she's powerful, she decides which reporting workflows even get to show up on Fedora. no cap. 🦋

---

✨ NAME ✨

report_fedora.conf — configuration file for libreport.

periodt, that's the whole name section, moving on 🎀

---

🌸 DESCRIPTION 🌸

so this config file is the one that says which of the reporting work flow definitions are applicable for all problems types on Fedora. like, every problem type. all of them. she's the bouncer at the club 💅

Every applicable work flow gets presented to users in the User Interface as a possibility for processing any problem. a work flow becomes applicable when its conditions are satisfied — that's the vibe check, and only the ones who pass get in ✨

The file is built from one condition per line. one. per. line. no cramming, no multitasking 🙈

Every single condition line must start with:

EVENT=workflow_NAME

where "workflow_" is a constant prefix (she never changes, iconic behavior) and "workflow_NAME" is the base name of the path to the reporting work flow configuration file.

The rest of the condition line has one of these forms:

• VAR=VAL
• VAR!=VAL
• VAL~=REGEX

and VAR here is the name of a problem directory element that's getting checked — think "executable", "package", "hostname" etc. and the condition can consist of as many element checks as it is necessary. go off, stack them, she can handle it 👑

---

🔥 EXAMPLES 🔥

condition line:

EVENT=workflow_FedoraCCpp analyzer=CCpp

The condition line above expects existence of:

/usr/share/libreport/workflows/workflow_FedoraCCpp.xml

like, she's literally checking that this file exists before she lets the workflow through. simple as that, and it ate 💅

---

🫶 SEE ALSO 🫶

• report-gtk(1)

---

👑 AUTHOR 👑

• ABRT team

---

LIBREPORT 2.17.15 · 09/19/2025 — mwah, that's a wrap bestie, go configure something cute 💖✨🎀🦋