From Fedora Project Wiki

No edit summary
No edit summary
(5 intermediate revisions by 4 users not shown)
Line 3: Line 3:
|actions=
|actions=
# Ensure you have the plugin installed with the command {{command|su -c 'yum install libreport-plugin-mailx'}}
# Ensure you have the plugin installed with the command {{command|su -c 'yum install libreport-plugin-mailx'}}
# Ensure you have sendmail installed with the command {{command|su -c 'yum install sendmail'}}
# Ensure that the ''abrtd'' and ''abrt-applet'' processes are both running
# Ensure 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
# Click on the pop-up notification to start ''abrt-gui''
# Start gnome-abrt (either from cmdline or from application menu).
# Select the entry matching the recently crashed application, then choose '''Problem > Open problem data''' in main menu.  
# Select the entry matching the recently crashed application, then choose '''Analyze'''.  
# At reporting step, choose '''Mailx''' as a reporting event
# At reporting step, choose '''Mailx''' as a reporting event
# 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.
# Use '''Preferences''' button in the same window to configure the plugin, set your email as the recipient.  
# 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/tmp/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.
# Check the the email if the message from ABRT has arrived (might take a few minutes).
# In terminal, make sure {{command|whoami}} says you are <tt>USER</tt> and then run command {{command|mail}} -- you should see new mail starting "[abrt] ..."
}}
}}
[[Category:Package_abrt_test_cases]]
[[Category:Package_abrt_test_cases]]

Revision as of 12:39, 7 May 2013

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 you have sendmail installed with the command su -c 'yum install sendmail'
  3. Ensure that the abrtd and abrt-applet processes are both running
  4. Kill a running process with the command kill -SIGSEGV (pid). It must be a process that is part of a signed Fedora package
  5. Start gnome-abrt (either from cmdline or from application menu).
  6. Select the entry matching the recently crashed application, then choose Analyze.
  7. At reporting step, choose Mailx as a reporting event
  8. Use Preferences button in the same window to configure the plugin, set your email as the recipient.
  9. Proceed to reporting using "Forward"/"Apply" buttons.
  10. 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/tmp/abrt/ccpp-2011-03-04-15:46:26-22496/event_log).

Expected Results

  1. Check the the email if the message from ABRT has arrived (might take a few minutes).