From Fedora Project Wiki
< Features
No edit summary |
|||
| (14 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
= ABRT = | = ABRT 1.0 = | ||
== Summary == | == Summary == | ||
<!-- A sentence or two summarizing what this feature is and what it will do. This information is used for the overall feature summary page for each release. --> | <!-- A sentence or two summarizing what this feature is and what it will do. This information is used for the overall feature summary page for each release. --> | ||
The tool to help non-power users with bug reporting, making it as easy as a few mouse clicks. | 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. | ||
== Owner == | == Owner == | ||
| Line 14: | Line 13: | ||
== Current status == | == Current status == | ||
* Targeted release: [[Releases/12 | Fedora 12]] | * Targeted release: [[Releases/12 | Fedora 12]] | ||
* Last Updated: 2009-08-03 | |||
* Percentage of completion: 100% | * Percentage of completion: 100% | ||
== Detailed Description == | == Detailed Description == | ||
<!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. --> | <!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. --> | ||
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 == | == Benefit to Fedora == | ||
<!-- What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new feature, what capabilities does it bring? Why will Fedora become a better distribution or project because of this feature?--> | <!-- What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new feature, what capabilities does it bring? Why will Fedora become a better distribution or project because of this feature?--> | ||
Ease of bug reporting and quick response from maintainers based on info from | 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. | ||
== Scope == | == Scope == | ||
<!-- What work do the developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | <!-- What work do the developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | ||
what is already done: | |||
* daemon for detecting crashes | * daemon for detecting crashes | ||
* | * pluginable architecture: | ||
* system detecting if binary belongs to our package | ** 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 | |||
* GUI | |||
* compiled (C/C++) programs support | |||
* Python support | |||
It shouldn't affect any part of Fedora, | further plans: | ||
* 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 == | == How To Test == | ||
| Line 53: | Line 66: | ||
--> | --> | ||
* | |||
=== install abrt and plugins === | |||
<pre>$ yum install abrt*</pre> | |||
=== start the daemon (as root) === | |||
<pre># /etc/init.d/abrt start</pre> | |||
=== start the notification applet === | |||
<pre>$ abrt-applet &</pre> | |||
=== test the functionality === | |||
Now if something crashes, abrt will | |||
handle the crash. If you want to | |||
test this, crash something, for example: | |||
<pre> | |||
$ xfontsel & | |||
$ killall -6 xfontsel | |||
</pre> | |||
An icon will appear in the | |||
notification area. | |||
You can now run the GUI: | |||
<pre> | |||
$ abrt-gui & | |||
</pre> | |||
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. | |||
== User Experience == | == User Experience == | ||
| Line 68: | Line 118: | ||
* PackageKit | * PackageKit | ||
* PolicyKit | * PolicyKit | ||
* sqlite | * sqlite | ||
* gtkmm | * gtkmm | ||
* Python | * Python | ||
* glade | * glade | ||
* 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 | |||
== Contingency Plan == | == Contingency Plan == | ||
| Line 87: | Line 138: | ||
<!-- The Fedora Release Notes inform end-users about what is new in the release. Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ --> | <!-- The Fedora Release Notes inform end-users about what is new in the release. Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ --> | ||
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the documentation team and shipped with the release. --> | <!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the documentation team and shipped with the release. --> | ||
== Comments and Discussion == | |||
* See [[Talk:Features/YourFeatureName]] <!-- This adds a link to the "discussion" tab associated with your page. This provides the ability to have ongoing comments or conversation without bogging down the main feature page --> | |||
[[Category:FeatureAcceptedF12]] | |||
<!-- When your feature page is completed and ready for review --> | |||
<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler --> | |||
<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete--> | |||
<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process --> | |||
<!-- Note that the current Feature guidelines require useful Scope and Test Plans at certain milestones; QA is responsible for checking these, and will change this category as needed. --> | |||
Latest revision as of 10:53, 3 August 2009
ABRT 1.0
Summary
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.
Owner
- email: zprikryl@redhat.com, jmoskovc@redhat.com, dnovotny@redhat.com
Current status
- Targeted release: Fedora 12
- Last Updated: 2009-08-03
- Percentage of completion: 100%
Detailed Description
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.
Scope
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
- GUI
- compiled (C/C++) programs support
- Python support
further plans:
- 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.
User Experience
- 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.
Dependencies
- dbus
- gtk2
- PackageKit
- PolicyKit
- sqlite
- gtkmm
- Python
- glade
- 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
Contingency Plan
None necessary, revert to previous release behaviour :)
Documentation
Release Notes
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.
Comments and Discussion