From Fedora Project Wiki
No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
|description=This test case tests the functionality of the [[Features/ABRT|ABRT]] feature using the ''Logger'' plugin. | |description=This test case tests the functionality of the [[Features/ABRT|ABRT]] feature using the ''Logger'' plugin. | ||
|actions= | |actions= | ||
<pre>$ yum install abrt-plugin-logger</pre> | |||
Edit <code>/etc/abrt/abrt.conf</code> and list the ''Logger'' plugin in ''EnabledPlugins'', ''CCpp'' and ''Python'' lines (which will enable and activate it). For example: | Edit <code>/etc/abrt/abrt.conf</code> and list the ''Logger'' plugin in ''EnabledPlugins'', ''CCpp'' and ''Python'' lines (which will enable and activate it). For example: | ||
<pre> | <pre> | ||
Revision as of 12:03, 20 August 2009
Description
This test case tests the functionality of the ABRT feature using the Logger plugin.
How to test
$ yum install abrt-plugin-logger
Edit /etc/abrt/abrt.conf and list the Logger plugin in EnabledPlugins, CCpp and Python lines (which will enable and activate it). For example:
... EnabledPlugins = Logger, SQLite3, CCpp, Kerneloops, KerneloopsScanner, KerneloopsReporter, Bugzilla, Python #, Mailx ... CCpp = Bugzilla, Logger Python = Bugzilla, Logger ...
Make sure you have abrt-plugin-logger installed. Install this plugin if it's missing.
Restart ABRT:
# service abrt restart
And final steps are:
- Ensure that the abrt and abrt-applet processes are both running
- Kill a running process: kill -SIGSEGV (pid). It must be a process that is part of a signed Fedora package
- Click on the panel applet to start abrt-gui
- Select the entry matching the recently crashed application, then click on Report
- At the report window, click Send
Expected Results
- After you click Send, a notification window should report, among other things: "Logger: Report was stored into: /var/log/abrt-logger"