From Fedora Project Wiki

Revision as of 15:15, 31 March 2010 by Vda (talk | contribs)


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 and list the Bugzilla plugin in CCpp and Python lines (which will enable and activate it). For example:
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
Enabled = yes
BugzillaURL =
NoSSLVerify = yes
#enter your login here
Login =
#enter your password here
Password =
  • Optionally, you may set up the username and password using abrt-gui. Launch abrt-gui and select Edit -> Plugins, find Bugzilla in the list, press Configure plugin. Once complete, you may check using seahorse tool that data is saved in Gnome keyring (in seahorse, in should be on "Passwords" tab).
  • Restart ABRT:
    $ service abrt restart
  • 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, click Report
  • At the report window, click Send

Expected Results

  1. A popup message should say: "Bugzilla:"
  2. A bug entry should be filled in the Bugzilla, the entry should be assigned to the package you crashed.
  3. Now it might be a good idea to close the entry in Bugzilla since this "crash" was created during testing by us, it's important to prevent making package maintainer upset by a bunch of bogus bugzilla records.