From Fedora Project Wiki

Revision as of 17:24, 29 March 2011 by Adamwill (talk | contribs) (minor cleanups)


This test case tests the functionality of the ABRT feature using the Logger reporting 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_event.conf and be sure you have there e.g. EVENT=report_Logger abrt-action-print -o "${Log_File:-/var/log/abrt.log}". This is the default, so if you are running a clean live image or have not manually re-configured abrt, it should be there
  3. If you had to change the file, restart ABRT with the command su -c 'systemctl restart abrtd.service'
  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 Open
  8. When you reach reporter selector page, select Logger
  9. Use "Configure Events" button in the same window to change log file path. The default path, /var/log/abrt.log, is usually not writable by regular users, so pick somewhere inside your home directory. The file does not have to exist, it will be created
  10. Click through to the last window of the wizard

Expected Results

  1. After you finish the steps in wizard at the last screen you should see "The report was stored to <FILENAME>"
  2. Open the log file and see if crash information is in it and is well-formatted