From Fedora Project Wiki

m (Updated wiki syntax)
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=
Ensure you have the plugin installed:
+
# Ensure you have the plugin installed:
<pre>yum install abrt-plugin-logger</pre>
+
#: <pre>yum install abrt-plugin-logger</pre>
 
+
# Edit <code>/etc/abrt/abrt.conf</code> and be sure the ''Logger'' plugin in the following sections ''EnabledPlugins'', ''CCpp'' and ''Python''. 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>
+
#: ...
...
+
#: EnabledPlugins = Logger, SQLite3, CCpp, Kerneloops, KerneloopsScanner, KerneloopsReporter, Bugzilla, Python #, Mailx
EnabledPlugins = Logger, SQLite3, CCpp, Kerneloops, KerneloopsScanner, KerneloopsReporter, Bugzilla, Python #, Mailx
+
#: ...
...
+
#: CCpp = Bugzilla, Logger
CCpp = Bugzilla, Logger
+
#: Python = Bugzilla, Logger
Python = Bugzilla, Logger
+
#: ...
...
+
#: </pre>
</pre>
+
# Restart ABRT: <pre># service abrt restart</pre>
Make sure you have abrt-plugin-logger installed. Install this plugin if it's missing.
+
# Confirm that the ''abrt'' and ''abrt-applet'' processes are both running
Restart ABRT: <pre># service abrt restart</pre>
 
 
 
And final steps are:
 
# Ensure that the ''abrt'' and ''abrt-applet'' processes are both running
 
 
# Kill a running process: <tt>kill -SIGSEGV (pid)</tt>. It must be a process that is part of a signed Fedora package
 
# Kill a running process: <tt>kill -SIGSEGV (pid)</tt>. It must be a process that is part of a signed Fedora package
 
# Click on the panel applet to start ''abrt-gui''
 
# Click on the panel applet to start ''abrt-gui''

Revision as of 17:00, 20 August 2009

Description

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


How to test

  1. Ensure you have the plugin installed:
    yum install abrt-plugin-logger
  2. Edit /etc/abrt/abrt.conf and be sure the Logger plugin in the following sections EnabledPlugins, CCpp and Python. For example:
    ...
    EnabledPlugins = Logger, SQLite3, CCpp, Kerneloops, KerneloopsScanner, KerneloopsReporter, Bugzilla, Python #, Mailx
    ...
    CCpp = Bugzilla, Logger
    Python = Bugzilla, Logger
    ...
  3. Restart ABRT:
    # service abrt restart
  4. Confirm that the abrt and abrt-applet processes are both running
  5. Kill a running process: kill -SIGSEGV (pid). It must be a process that is part of a signed Fedora package
  6. Click on the panel applet to start abrt-gui
  7. Select the entry matching the recently crashed application, then click on Report
  8. 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"