From Fedora Project Wiki

Revision as of 10:23, 20 January 2009 by Zprikryl (talk | contribs) (New page: = Feature Name = <!-- The name of your feature --> CrashCatcher == Summary == <!-- A sentence or two summarizing what this feature is and what it will do. This information is used for th...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Feature Name

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

Current status

  • Targeted release: Releases/11
  • Last updated: 20.1.2009
  • Percentage of completion: 10%

Detailed Description

This feature should help users to detect defects in applications written and to create a bug report with all informations needed by maintainer to fix it. It's heavilly pluginable so, it can be used for any language and bug reporting system (trac, BZ, ...)

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

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 CrashCatcher with at least one language plugin.
  • Run some app. This app has to be written in same language as language plugin.
  • kill -9 <pid of app>
  • See if CrashCatcher detects it.

User Experience

Dependencies

  • dbus
  • gtk2
  • PackageKit
  • PoliceKit

Contingency Plan

None necessary, revert to previous release behaviour :)

Documentation

[1] CrashCather home page.

Release Notes

Comments and Discussion