m (Features/CrashCatcher moved to Features/ABRT) |
(→Documentation: fix redlink, clean up HTML comment) |
||
| (7 intermediate revisions by 7 users not shown) | |||
| Line 21: | Line 21: | ||
== 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. --> | ||
This feature semi-automatically provides information about defects and crashes on user system. It collects necessary data about the crash, generates a report with all information and based on user interaction sends it to some bug reporting system. The | This feature semi-automatically provides information about defects and crashes on user system. It collects necessary data about the crash, generates a report with all information and based on user interaction sends it to some bug reporting system. The goal is to have this tool heavily plugin-able - so it can be used for any compiled/scripting language and bug reporting system (trac, BZ, 3rd party bug reporting tool ...) | ||
== 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 == | ||
| Line 55: | Line 55: | ||
--> | --> | ||
* Install | * Install ABRT with C/C++ language plugin. | ||
* Run some app. This app has to be written in C or C++. | * Run some app. This app has to be written in C or C++. | ||
* kill -s SIGSEGV <pid of app> | * kill -s SIGSEGV <pid of app> | ||
* See if | * See if ABRT detects it. | ||
== User Experience == | == User Experience == | ||
| Line 81: | Line 81: | ||
== Documentation == | == Documentation == | ||
* [https://fedorahosted.org/abrt/wiki abrt home page] | |||
* [ | * Setup and test docs from the test days: | ||
** [[QA/Test_Days/2009-02-26]] | |||
** [[Test Day:2009-08-20 ABRT]] | |||
* [[http://fedoraproject.org/w/uploads/a/ab/ABRT.odp ABRT FUDCon Berlin 2009 presentation]] | |||
== Release Notes == | == Release Notes == | ||
| Line 92: | Line 95: | ||
== Comments and Discussion == | == Comments and Discussion == | ||
* See [[Talk:Features/ | * See [[Talk:Features/ABRT]] <!-- 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:FeatureAcceptedF11]] | [[Category:FeatureAcceptedF11]] | ||
Latest revision as of 21:27, 7 October 2009
ABRT
IMPORTANT NOTE!! -> THIS PROJECT HAS BEEN RENAMED TO ABRT - Automatic Bug Reporting Tool (previously known as CrashCatcher)
Summary
The tool to help non-power users with bug reporting, making it as easy as a few mouse clicks.
Owner
- Name: Zdenek Prikryl Jiri Moskovcak
- email: zprikryl@redhat.com, jmoskovc@redhat.com
Current status
- Targeted release: Fedora 11
- Last updated: 2009-03-05
- Percentage of completion: 100%
Detailed Description
This feature semi-automatically provides information about defects and crashes on user system. It collects necessary data about the crash, generates a report with all information and based on user interaction sends it to some bug reporting system. The goal is to have this tool heavily plugin-able - so it can be used for any compiled/scripting language and bug reporting system (trac, BZ, 3rd party bug reporting tool ...)
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 has to be done:
- pluginable architecture
- daemon for detecting crashes
- authentication system
- system detecting if binary belongs to our package (PackageKit support)
- add-ons for languages
- plugins for reporters, databases of crashes, specific applications
- GUI and TUI
It shouldn't affect any part of Fedora, it's desing allows to easilly disable or remove this application completelly.
How To Test
- Install ABRT with C/C++ language plugin.
- Run some app. This app has to be written in C or C++.
- kill -s SIGSEGV <pid of app>
- See if ABRT detects it.
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
- Archer
- sqlite
- gtkmm
- Python
- glade
Contingency Plan
None necessary, revert to previous release behaviour :)
Documentation
- abrt home page
- Setup and test docs from the test days:
- [ABRT FUDCon Berlin 2009 presentation]
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.