From Fedora Project Wiki
(match > abrt-0.0.4) |
No edit summary |
||
Line 16: | Line 16: | ||
# Database | # Database | ||
Database = SQLite3 | Database = SQLite3 | ||
[ AnalyzerActionsAndReporters ] | |||
CCpp = Bugzilla, Logger | |||
</pre> | </pre> | ||
Restart ABRT: <pre># service abrt restart</pre> | Restart ABRT: <pre># service abrt restart</pre> |
Revision as of 08:56, 18 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 to enable and activate the Logger plugin in Common section. 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, select Generate
- At the report window, click Apply
Expected Results
- A crash log should be reported by the Logger plugin into /var/log/abrt-logger