This test case tests the functionality of the ABRT feature using the Bugzilla plugin.
How to test
- If you don't have an account on the bugzilla, create one.
- Edit /etc/abrt/abrt.conf to enable and activate the Bugzilla plugin. A sample config is noted below
# common abrt settings [ Common ] # enabled plugins # there has to be exactly one database plugin EnabledPlugins = Bugzilla, Mailx, SQLite3, CCpp, Logger, Kerneloops, KerneloopsScanner, KerneloopsReporter, Python # reporters association with analyzers [ AnalyzerActionsAndReporters ] CCpp = Mailx, Bugzilla, Logger Python = Mailx, Bugzilla, Logger
- Edit ~/.abrt/Bugzilla.conf and make sure the configuration is valid. Insert your bugzilla username and password
BugzillaURL = https://bugzilla.redhat.com/xmlrpc.cgi NoSSLVerify = yes #enter your login here Login = #enter your password here Password =
Optionally you may set up the username/password pair via abrt-gui -> Edit -> Preferences -> Enable Bugzilla -> Configure plugin and check that ~/.abrt/Bugzilla.conf is correct.
# 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 Send
- A bug entry should be filled in the Bugzilla, the entry should be assigned to the package you crashed.
- Now it might be a good idea to close the entry in Bugzilla WWW since this "crash" was intended and produced by us, so, package maintained won't get upset by a bunch of bogus crashes.