From Fedora Project Wiki
No edit summary |
(understandability) |
||
Line 2: | Line 2: | ||
|description=This test case tests the functionality of the [[Features/ABRT|ABRT]] feature using the ''Logger'' plugin. | |description=This test case tests the functionality of the [[Features/ABRT|ABRT]] feature using the ''Logger'' plugin. | ||
|actions= | |actions= | ||
Edit | Edit <code>/etc/abrt/abrt.conf</code> and list the ''Logger'' plugin in ''EnabledPlugins'' and ''CCpp'' lines (which will enable and activate it). A sample config is noted below: | ||
<pre> | <pre> | ||
[ Common ] | [ Common ] |
Revision as of 13:29, 19 August 2009
Description
This test case tests the functionality of the ABRT feature using the Logger plugin.
How to test
Edit /etc/abrt/abrt.conf
and list the Logger plugin in EnabledPlugins and CCpp lines (which will enable and activate it). A sample config is noted below:
[ Common ] # Enable GPG check EnableOpenGPG = no # GPG keys OpenGPGPublicKeys = /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora # blacklisted packages BlackList = # enabled plugins # there has to be exactly one database plugin EnabledPlugins = Logger, SQLite3, CCpp, Kerneloops, KerneloopsScanner, KerneloopsReporter, Bugzilla, Python #, Mailx # Database Database = SQLite3 [ AnalyzerActionsAndReporters ] CCpp = Bugzilla, Logger
Restart ABRT:
# service abrt restart
And final steps are:
- Ensure that the abrt and abrt-applet processes are both running
- Kill a running process: 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
- At the report window, click Send
Expected Results
- After you click Send, a notification window should report, among other things: "Logger: Report was stored into: /var/log/abrt-logger"