From Fedora Project Wiki

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=
Edit <code>/etc/abrt/abrt.conf</code> and list the ''Logger'' plugin in ''EnabledPlugins'' and ''CCpp'' 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>
 
...
 
...
Line 8: Line 8:
 
...
 
...
 
CCpp = Bugzilla, Logger
 
CCpp = Bugzilla, Logger
 +
Python = Bugzilla, Logger
 
...
 
...
 
</pre>
 
</pre>

Revision as of 09:08, 20 August 2009

Description

This test case tests the functionality of the ABRT feature using the Logger plugin.


How to test

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
...

Restart ABRT:

# service abrt restart

And final steps are:

  1. Ensure that the abrt and abrt-applet processes are both running
  2. Kill a running process: kill -SIGSEGV (pid). It must be a process that is part of a signed Fedora package
  3. Click on the panel applet to start abrt-gui
  4. Select the entry matching the recently crashed application, then click on Report
  5. At the report window, click Send

Expected Results

  1. After you click Send, a notification window should report, among other things: "Logger: Report was stored into: /var/log/abrt-logger"