REPORT-GTK(1)

💖 REPORT-GTK 💖

okay bestie, so this one is report-gtk, part of the LIBREPORT MANUAL lineup, and it's literally the little GUI queen that helps you look at crashes and send them off into the world. let's get into it 🫶

---

✨ NAME ✨

report-gtk — a GUI tool to analyze and report ABRT problems 💅

---

🎀 SYNOPSIS 🎀

report-gtk [-vpdx] [-e EVENT] [-g GUI_FILE] PROBLEM_DIR

---

🦋 DESCRIPTION 🦋

so report-gtk is a graphical tool, like with actual windows and buttons, and its whole job is reporting application crashes and other problems — the ones caught by the abrtd daemon, or the ones created by other programs using libreport. no cap.

it works with one single problem saved in the specified PROBLEM_DIR. one problem, one directory, that's the vibe.

and then in expert mode? it enables access to and manipulation of problem data. main character energy fr fr 👑

---

🌸 OPTIONS 🌸

• -d, --delete — Remove PROBLEM_DIR after reporting. like, bye bestie, we're done here 💀
• -e EVENT — Run only theset EVENTs on PROBLEM_DIR
• -g FILE — Alternate GUI file
• -p — Add program names to log
• -v, --verbose — Be verbose (yes, tell me everything, I'm obsessed with details)
• -V, --version — Display version and exit
• -x, --expert — Enabled advanced features

---

⭐ CONFIGURATION ⭐

💬 Dialogue answers 💬

During the reporting process report-gtk might show a dialogue asking for a decision to be made. some of those dialogues provides an option to remember the answer. and if it is requested to remember the answer, report-gtk saves the answer in

$XDG_CONFIG_HOME/abrt/settings/report-gtk.conf

If $XDG_CONFIG_HOME is not set, $HOME/.config is used instead. simple as that 🎀

🔍 Sensitive data search 🔍

See forbidden_words.conf(5), ignored_words.conf(5) and ignored_elements.conf(5)

🧚 Reporting work flow configuration 🧚

These configuration files are placed in /usr/share/libreport/workflows.

Each file has XML formatting with the following DTD:

<!ELEMENT workflow    (name+,description+,priority?,events*)>
<!ELEMENT name        (#PCDATA)>
<!ATTLIST name         xml:lang CDATA #IMPLIED>
<!ELEMENT description (#PCDATA)>
<!ATTLIST description  xml:lang CDATA #IMPLIED>
<!ELEMENT priority =  (#PCDATA)>
<!ELEMENT events =    (event)+>
<!ELEMENT event =     (#PCDATA)>

• name — User visible name
• description — User visible description
• priority — Priority of the workflow. Higher number means a more visible place in UI. If not provided, 0 is used. The value is signed integer.
• events — List of executed events
• event — Name of event. If event is not applicable on the problem data or if it is not defined then process continues with next event sibling.

---

🌈 EXAMPLES 🌈

🍓 Simple reporting work flow 🍓

<workflow>
  <name xml:lang="en">Example</name>
  <name xml:lang="cs">Příklad</name>
  <description xml:lang="en">Example description</description>
  <description xml:lang="cs">Příklad popisu</description>
  <priority>10</priority>
  <evetns>
     <event>analyze_example</event>
     <event>collect_example</event>
     <event>report_example</event>
  </events>
</workflow>

---

👀 SEE ALSO 👀

forbidden_words.conf(5), ignored_words.conf(5), ignored_elements.conf(5)

---

👑 AUTHORS 👑

• ABRT team

---

and that's the whole page, bestie!! this is LIBREPORT 2.17.15, dated 09/19/2025, and honestly? iconic. go report some problems (the software kind, not your ex) 💜✨🎀