1. Automated Bug Reporting Tool
Radek Vokál
Zdeněk Přikryl

2. What is it about? ABRT [abort]
Automated bug reporting tool for non-power users
Make it easy for users, make it useful for developers
Most users don't write bug reports
Most developers ask for additional data from reporters
Help admins to collect information about their systems
Help developers/maintainers/support organizations to collect valuable data
Better support for users/customers etc
"Abort" is antiquated German for a toilet.

3. Why is it needed? We have users, not developers using the OS
Not every users knows how to work with gdb, debuginfos etc
Every application/bug needs background
A user doesn't know what's important for developer
Application/bug might require additional info
User doesn't know how to reproduce the crash
Most users are not capable of reproducing the crash
Developers need data at the time of the crash
Faster bug resolving
No need to wait for reporter answers
Useful data from the first crash, no need for second run

4. Architecture overview
Add-on can detects malfunctions in a particular type of applications
Currently there are add-ons for C/C++, Python and kerneloops
Plugin does specific function(s) according to its type
Reporters have different targets for reporting ( , bugzilla, 3rd party ticketing software, ...)
Actions performs particular tasks (gets additional info [sosreport], ...)
Core components are basic I/O points.
e.g.: applet for bug notification, GUI/CLI for getting bug details, ...

5. Detailed architecture

6. Main window

7. Report window

8. Where does it live? How to use it?
Packages are in Fedora 11
(in repos there is buggy old version, the new one will be there soon)
Main configuration file is in /etc/abrt/abrt.conf
See man abrt.conf(7) for more information
Plugin can have its own configuration file in /etc/abrt/plugins/*
Reporters can have config file in $HOME/.abrt/* too
Latest versions in rawhide
Documentation about plans, tests, etc

9. Questions?