report-gtk(1)

1REPORT-GTK(1)                  LIBREPORT MANUAL                  REPORT-GTK(1)
2
3
4

NAME

6       report-gtk - GUI tool to analyze and report ABRT problems
7

SYNOPSIS

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

DESCRIPTION

12       report-gtk is a graphical tool that reports application crashes and
13       other problems caught by abrtd daemon, or created by other programs
14       using libreport. report-gtk works with a single problem saved in
15       specified PROBLEM_DIR. In the expert mode it enables access to and
16       manipulation of problem data.
17

OPTIONS

19       -d, --delete
20           Remove PROBLEM_DIR after reporting
21
22       -e EVENT
23           Run only theset EVENTs on PROBLEM_DIR
24
25       -g FILE
26           Alternate GUI file
27
28       -p
29           Add program names to log
30
31       -v, --verbose
32           Be verbose
33
34       -V, --version
35           Display version and exit
36
37       -x, --expert
38           Enabled advanced features
39

CONFIGURATION

41   Dialogue answers
42       During the reporting process report-gtk might show a dialogue asking
43       for a decision to be made. Some of those dialogues provides an option
44       to remember the answer. If it is requested to remember the answer,
45       report-gtk saves the answer in
46       $XDG_CONFIG_HOME/abrt/settings/report-gtk.conf
47
48       If $XDG_CONFIG_HOME is not set, $HOME/.config is used instead.
49
50   Sensitive data search
51       See forbidden_words.conf(5) and ignored_words.conf(5)
52
53   Reporting work flow configuration
54       These configuration files are placed in /usr/share/libreport/workflows.
55
56       Each file has XML formatting with the following DTD:
57
58           <!ELEMENT workflow    (name+,description+,priority?,events*)>
59           <!ELEMENT name        (#PCDATA)>
60           <!ATTLIST name         xml:lang CDATA #IMPLIED>
61           <!ELEMENT description (#PCDATA)>
62           <!ATTLIST description  xml:lang CDATA #IMPLIED>
63           <!ELEMENT priority =  (#PCDATA)>
64           <!ELEMENT events =    (event)+>
65           <!ELEMENT event =     (#PCDATA)>
66
67       name
68           User visible name
69
70       description
71           User visible description
72
73       priority
74           Priority of the workflow. Higher number means a more visible place
75           in UI. If not provided, 0 is used. The value is signed integer.
76
77       events
78           List of executed events
79
80       event
81           Name of event. If event is not applicable on the problem data or if
82           it is not defined then process continues with next event sibling.
83

EXAMPLES

85   Simple reporting work flow
86           <workflow>
87             <name xml:lang="en">Example</name>
88             <name xml:lang="cs">Příklad</name>
89             <description xml:lang="en">Example description</description>
90             <description xml:lang="cs">Příklad popisu</description>
91             <priority>10</priority>
92             <evetns>
93                <event>analyze_example</event>
94                <event>collect_example</event>
95                <event>report_example</event>
96             </events>
97           </workflow>
98

AUTHORS

103       ·   ABRT team
104
105
106
107LIBREPORT 2.9.5                   08/10/2019                     REPORT-GTK(1)