From Fedora Project Wiki
No edit summary |
No edit summary |
||
Line 10: | Line 10: | ||
#:... | #:... | ||
#:</pre> | #:</pre> | ||
# Restart ABRT | # Restart ABRT with the command {{command|su -c 'service abrtd restart'}} | ||
# Confirm that the ''abrtd'' and ''abrt-applet'' processes are both running | # Confirm 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 |
Revision as of 08:12, 1 April 2010
Description
This test case tests the functionality of the ABRT feature using the Logger plugin.
How to test
- Ensure you have the plugin installed with the command
su -c 'yum install abrt-plugin-logger'
- Edit
/etc/abrt/abrt.conf
and be sure the Logger plugin is enabled in the CCpp and Python sections. For example:- ...
- CCpp = Bugzilla, Logger
- Python = Bugzilla, Logger
- ...
- Restart ABRT with the command
su -c 'service abrtd restart'
- Confirm that the abrtd and abrt-applet processes are both running
- Kill a running process with the command
kill -SIGSEGV (pid)
. 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, then click on Report, select Logger plugin.
- At the report window, click Send
Expected Results
- After you click Send, a notification window should report: "Logger: Report was stored into: /var/log/abrt-logger"
- The crash information should in fact be added to that file