From Fedora Project Wiki

 
(24 intermediate revisions by 10 users not shown)
Line 1: Line 1:
{{QA/Test_Case
{{QA/Test_Case
|description=This test case tests the functionality of the [[Features/ABRT|ABRT]] feature using the ''Mailx'' plugin.
|description=This test case tests the functionality of the ABRT feature using the ''Mailx'' plugin.
|actions=
|actions=
* Edit ''/etc/abrt/abrt.conf'' to enable and activate the ''Mailx'' plugin. A sample config is noted below
<ol>
<pre>
  <li>Ensure you have the plugin installed with the command {{command|su -c 'dnf install libreport-plugin-mailx'}}</li>
...
  <li>Ensure you have sendmail installed with the command {{command|su -c 'dnf install sendmail'}}</li>
EnabledPlugins = Mailx, SQLite3, CCpp, Logger, Kerneloops, KerneloopsScanner, KerneloopsReporter, Bugzilla, Python
  <li>Ensure that the ''abrtd'' and ''abrt-applet'' processes are both running</li>
...
  <li>Turn on the mailx workflow <pre>sudo sed -i 's/# EVENT/EVENT/' /etc/libreport/workflows.d/report_mailx.conf</pre></li>
CCpp = Mailx, Bugzilla, Logger
  <li>Kill some running process: <tt>kill -SIGSEGV (pid)</tt> or run {{command|will_segfault}}. It must be a process that is part of a signed Fedora package</li>
Python = Mailx, Bugzilla, Logger
  <li>Start gnome-abrt (either from cmdline or from application menu)</li>
...
  <li>Select the entry matching the recently crashed application, then choose '''Report'''</li>
</pre>
  <li>At reporting step, choose '''Send the problem data via email''' as a reporting event</li>
* Edit ''/etc/abrt/plugins/Mailx.conf'' and make sure the configuration is valid. The default configuration:
  <li>Update Subject, Sender and Recepient</li>
<pre>
  <li>Proceed to reporting using "Forward"/"Apply" buttons</li>
# Configuration to Email reporter plugin
  <li>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}})</li>
# Parameters
</ol>
Parameters =
 
# Your Email
EmailFrom = user@localhost
 
# Email To
EmailTo = root@localhost
 
# Warning! enabling this may cause sending a lot of MB via email
SendBinaryData = no
</pre>
should work. Only change the EmailTo address to a public address that would require forwarding through a real SMTP server if you have the 'mailx' configuration set so that such mails are correctly handled.
 
* Restart ABRT: <pre># service abrt restart</pre>
 
* Make sure sendmail service is running: <pre># service sendmail start</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
# Click on the panel applet to start ''abrt-gui''
# Select the entry matching the recently crashed application, click '''Report'''
# At the report window, click '''Send'''
|results=
|results=
# A mail reporting the crash should be sent to the email address specified in ''/etc/abrt/plugins/Mailx.conf''. If you left this set to ''root@localhost'', you should be able to see the mail in the file ''/var/spool/mail/root'' in a default Fedora setup or via command ''mail'' as a root.
# Check the the email if the message from ABRT has arrived (might take a few minutes).
}}
}}
[[Category:ABRT_Test_Cases]]
[[Category:Package_abrt_test_cases]]

Latest revision as of 11:42, 10 April 2015

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 'dnf install libreport-plugin-mailx'
  2. Ensure you have sendmail installed with the command su -c 'dnf install sendmail'
  3. Ensure that the abrtd and abrt-applet processes are both running
  4. Turn on the mailx workflow
    sudo sed -i 's/# EVENT/EVENT/' /etc/libreport/workflows.d/report_mailx.conf
  5. Kill some running process: kill -SIGSEGV (pid) or run will_segfault. It must be a process that is part of a signed Fedora package
  6. Start gnome-abrt (either from cmdline or from application menu)
  7. Select the entry matching the recently crashed application, then choose Report
  8. At reporting step, choose Send the problem data via email as a reporting event
  9. Update Subject, Sender and Recepient
  10. Proceed to reporting using "Forward"/"Apply" buttons
  11. 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).