From Fedora Project Wiki

(/var/spool/abrt -> /var/tmp/abrt)
 
(4 intermediate revisions by 2 users not shown)
Line 2: Line 2:
 
|description=This test case tests the functionality of the ABRT feature using the ''Mailx'' plugin.
 
|description=This test case tests the functionality of the ABRT feature using the ''Mailx'' plugin.
 
|actions=
 
|actions=
# Ensure you have the plugin installed with the command {{command|su -c 'yum install libreport-plugin-mailx'}}
+
<ol>
# Ensure that the ''abrtd'' and ''abrt-applet'' processes are both running
+
  <li>Ensure you have the plugin installed with the command {{command|su -c 'dnf install libreport-plugin-mailx'}}</li>
# Kill a running process with the command {{command|kill -SIGSEGV (pid)}}. It must be a process that is part of a signed Fedora package
+
  <li>Ensure you have sendmail installed with the command {{command|su -c 'dnf install sendmail'}}</li>
# Click on the pop-up notification to start ''abrt-gui''
+
  <li>Ensure that the ''abrtd'' and ''abrt-applet'' processes are both running</li>
# Select the entry matching the recently crashed application, then choose '''Problem > Open problem data''' in main menu.
+
  <li>Turn on the mailx workflow <pre>sudo sed -i 's/# EVENT/EVENT/' /etc/libreport/workflows.d/report_mailx.conf</pre></li>
# At reporting step, choose '''Mailx''' as a reporting event
+
  <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>
# Use "Preferences" button in the same window to configure the plugin, set local machine user's name as the recipient.
+
  <li>Start gnome-abrt (either from cmdline or from application menu)</li>
# Proceed to reporting using "Forward"/"Apply" buttons
+
  <li>Select the entry matching the recently crashed application, then choose '''Report'''</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>At reporting step, choose '''Send the problem data via email''' as a reporting event</li>
 +
  <li>Update Subject, Sender and Recepient</li>
 +
  <li>Proceed to reporting using "Forward"/"Apply" buttons</li>
 +
  <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>
 +
</ol>
 
|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]]

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).