Features/ABRTF12

From FedoraProject

< Features(Difference between revisions)
Jump to: navigation, search
(Created page with '= ABRT = IMPORTANT NOTE!! -> THIS PROJECT HAS BEEN RENAMED TO ABRT - Automatic Bug Reporting Tool (previously known as CrashCatcher) == Summary == <!-- A sentence or two summari...')
 
Line 8: Line 8:
 
== Owner ==
 
== Owner ==
 
<!--This should link to your home wiki page so we know who you are-->
 
<!--This should link to your home wiki page so we know who you are-->
* Name: [[User:zprikryl| Zdenek Prikryl]] [[User:jmoskovc| Jiri Moskovcak]]
+
* Name: [[User:zprikryl| Zdenek Prikryl]] [[User:jmoskovc| Jiri Moskovcak]] [[User:dnovotny| Daniel Novotny]]
  
 
<!-- Include you email address that you can be reached should people want to contact you about helping with your feature, status is requested, or  technical issues need to be resolved-->
 
<!-- Include you email address that you can be reached should people want to contact you about helping with your feature, status is requested, or  technical issues need to be resolved-->
* email: zprikryl@redhat.com, jmoskovc@redhat.com
+
* email: zprikryl@redhat.com, jmoskovc@redhat.com, dnovotny@redhat.com
  
 
== Current status ==
 
== Current status ==
 
<!-- CHANGE THE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. -->
 
<!-- CHANGE THE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. -->
* Targeted release: [[Releases/11 | Fedora 11]]  
+
* Targeted release: [[Releases/12 | Fedora 12]]  
* Last updated: 2009-03-05
+
 
* Percentage of completion: 100%
 
* Percentage of completion: 100%
  
Line 29: Line 28:
 
== 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 has to be done:
 
 
* pluginable architecture
 
* pluginable architecture
 
* daemon for detecting crashes
 
* daemon for detecting crashes
Line 83: Line 81:
 
<!-- Is there upstream documentation on this feature, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
 
<!-- Is there upstream documentation on this feature, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
 
* [https://fedorahosted.org/abrt/wiki abrt home page]
 
* [https://fedorahosted.org/abrt/wiki abrt home page]
* Setup and test docs from the test day: [[QA/Test_Days/2009-02-26]]
 
  
 
== Release Notes ==
 
== Release Notes ==

Revision as of 12:58, 8 July 2009

Contents

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

  • email: zprikryl@redhat.com, jmoskovc@redhat.com, dnovotny@redhat.com

Current status

  • Targeted release: Fedora 12
  • 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 CrashCatcher should make Fedora more stable and thus more attractive for users.

Scope

  • 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 CrashCatcher 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 CrashCatcher 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

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.