From Fedora Project Wiki

Line 10: Line 10:
 
#:...
 
#:...
 
#:</pre>
 
#:</pre>
# Restart ABRT with the command {{command|su -c 'service abrt restart'}}
+
# Restart ABRT daemon with the command {{command|su -c 'service abrtd restart'}}
 
# Confirm that the ''abrtd'' and ''abrt-applet'' processes are both running
 
# Confirm that the ''abrtd'' and ''abrt-applet'' processes are both running
 
# Kill a running process with the command {{command|kill -SIGSEGV (pid)}}. It must be a process that is part of a signed Fedora package
 
# Kill a running process with the command {{command|kill -SIGSEGV (pid)}}. It must be a process that is part of a signed Fedora package

Revision as of 08:11, 1 April 2010

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 with the command su -c 'yum install abrt-plugin-logger'
  2. Edit /etc/abrt/abrt.conf and be sure the Logger plugin is enabled in the CCpp and Python sections. For example:
    ...
    CCpp = Bugzilla, Logger
    Python = Bugzilla, Logger
    ...
  3. Restart ABRT daemon with the command su -c 'service abrtd restart'
  4. Confirm that the abrtd and abrt-applet processes are both running
  5. Kill a running process with the command 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, select Logger plugin.
  8. At the report window, click Send

Expected Results

  1. After you click Send, a notification window should report: "Logger: Report was stored into: /var/log/abrt-logger"
  2. The crash information should in fact be added to that file