(→Comments and Discussion)
|Line 121:||Line 121:|
== Contingency Plan ==
== Contingency Plan ==
Revision as of 16:19, 17 July 2009
- 1 ABRT 1.0
- 1.1 Summary
- 1.2 Owner
- 1.3 Current status
- 1.4 Detailed Description
- 1.5 Benefit to Fedora
- 1.6 Scope
- 1.7 How To Test
- 1.8 User Experience
- 1.9 Dependencies
- 1.10 Contingency Plan
- 1.11 Documentation
- 1.12 Release Notes
- 1.13 Comments and Discussion
The tool to help non-power users with bug reporting, making it as easy as a few mouse clicks. This version has a lot of improvements and fixes and is more user friendly.
- email: firstname.lastname@example.org, email@example.com, firstname.lastname@example.org
- Targeted release: Fedora 12
- Percentage of completion: 40%
abrt is a daemon that watches for application crashes. When a crash occurs, it collects the crash data (core file, application's command line etc.) and takes action according to the type of application that crashed and according to the configuration in the abrt.conf configuration file. There are plugins for various actions: for example to report the crash to Bugzilla, to mail the report, to transfer the report via FTP or SCP, or to run a specified application.
Benefit to Fedora
Ease of bug reporting and quick response from maintainers based on info from abrt should make Fedora more stable and thus more attractive for users.
what is already done:
- daemon for detecting crashes
- pluginable architecture:
- database plugin
- bugzilla plugin (report crash to bugzilla)
- file transfer plugin (transfer crash data via network)
- mailx plugin (send mail when crash happens)
- kernel oops plugin
- RunApp plugin (run arbitrary application when crash happens)
- system detecting if binary belongs to our package
- compiled (C/C++) programs support
- Python support
- improved GUI
- better integration with desktop
- better user authentication system
- add-ons for more languages
- central management
It shouldn't affect any part of Fedora, its desing allows to easily disable or remove this application completely.
How To Test
install abrt and plugins
$ yum install abrt*
start the daemon (as root)
# /etc/init.d/abrt start
start the notification applet
$ abrt-applet &
test the functionality
Now if something crashes, abrt will handle the crash. If you want to test this, crash something, for example:
$ xfontsel & $ killall -6 xfontsel
An icon will appear in the notification area.
You can now run the GUI:
$ abrt-gui &
select the crash, click "report" to report it, or click "delete" to delete it.
Note: for reporting to work, make sure you have a fully-updated system. Reporting uses -debuginfo packages, which have to match the version of the corresponding crashed program's packages. This also avoids reporting a bug which has already been fixed in a later version of the software.
- If an application crashes, the user is notified by a trayicon (or a message in a log) and a simple wizard will act as a guide through the bug reporting process. All required information is gathered automatically so bug reporting should be easy even for less experienced users.
- to turn abrt on by default, we need to change comps to install abrt by default and no longer install bug-buddy by default, the service needs to be enabled by default, and the applet needs to be autostarted at login
- abrt needs some better icons, request is here: https://fedorahosted.org/design-team/ticket/38
None necessary, revert to previous release behaviour :)
There is no simple tool for debugging programs and reporting bugs in Fedora and providing usefull information needed by package maintainer to fix a bug is often time-consuming and sometimes out of the skill range of an ordinary Fedora user. This tool should fill this gap and help users to fill a report with all required information in just a few mouse clicks.