From Fedora Project Wiki

No edit summary
No edit summary
Line 11: Line 11:
# Proceed to reporting using "Forward"/"Apply" buttons
# Proceed to reporting using "Forward"/"Apply" buttons
# If reporting is unsuccessful, please include the reporting log in your abrt bug report. Reporting log can be cut and pasted from the GUI report window, or retrieved from event_log file in problem data directory (e.g. {{filename|/var/spool/abrt/ccpp-2011-03-04-15:46:26-22496/event_log}}).
# If reporting is unsuccessful, please include the reporting log in your abrt bug report. Reporting log can be cut and pasted from the GUI report window, or retrieved from event_log file in problem data directory (e.g. {{filename|/var/spool/abrt/ccpp-2011-03-04-15:46:26-22496/event_log}}).
## In F15, mailx executable doesn't report any delivery errors. (If you are using Exim, check /var/log/exim/main.log if you don't get mail delivered). Thus, logs shown to abrt GUI users are nearly always useless...
|results=
|results=
# An email reporting the crash should be sent to USER@localhost unless specified otherwise.
# An email reporting the crash should be sent to USER@localhost unless specified otherwise.

Revision as of 17:24, 23 September 2011

Description

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


How to test

  1. Ensure you have the plugin installed with the command su -c 'yum install libreport-plugin-mailx'
  2. Ensure that the abrtd and abrt-applet processes are both running
  3. Kill a running process with the command kill -SIGSEGV (pid). It must be a process that is part of a signed Fedora package
  4. Click on the pop-up notification to start abrt-gui
  5. Select the entry matching the recently crashed application, click Open
  6. At reporting step, choose Mailx as a reporting event
  7. Use "Preferences" button in the same window to configure the plugin, set local machine user's name as the recipient. Note: root user may be blocked for local delivery. In Fedora 15, it is. Uses some other local user's name.
  8. Proceed to reporting using "Forward"/"Apply" buttons
  9. If reporting is unsuccessful, please include the reporting log in your abrt bug report. Reporting log can be cut and pasted from the GUI report window, or retrieved from event_log file in problem data directory (e.g. /var/spool/abrt/ccpp-2011-03-04-15:46:26-22496/event_log).
    1. In F15, mailx executable doesn't report any delivery errors. (If you are using Exim, check /var/log/exim/main.log if you don't get mail delivered). Thus, logs shown to abrt GUI users are nearly always useless...

Expected Results

  1. An email reporting the crash should be sent to USER@localhost unless specified otherwise.
  2. In terminal, make sure whoami says you are USER and then run command mail -- you should see new mail starting "[abrt] ..."