From Fedora Project Wiki

m (Add crash-catch yum repo instructions)
Line 46: Line 46:
 
# check if the daemon is really running, if not for some reason, run ''crash-catcher''
 
# check if the daemon is really running, if not for some reason, run ''crash-catcher''
 
# run ''cc-applet'' (as an ordinary user)
 
# run ''cc-applet'' (as an ordinary user)
 +
 +
rpm are available at [http://koji.fedoraproject.org/koji/taskinfo?taskID=1174255 rpms]
 +
 +
=== Configuration ===
 +
after installation some default settings are stored in /etc/crash-catcher/*
 +
configuration is written on single line "key = value {, value}"
 +
* main config file is /etc/crash-catcher/crash-catcher.conf
 +
  * OpenGPGPublicKeys list of GPG keys
 +
  * EnableOpenGPG, check if a package is signed with one of keys
 +
  * BlackList blacklisted backages
 +
  * EnabledPlugins a list of enabled plugis. There should to be at least one language/application plugin and database plugin
 +
  * Database denotes database plugin, there has to be one database plugin! (crash-catcher-plugin-sqlite3)
 +
  * every language/application plugin can have several reporter plugins. If you want to report something, then it has to have at least one :-)
 +
* Plugins conf files are in /etc/crash-catcher/plugins/*
 +
  * description of options is in these files.
 +
 +
=== Known issues ===
 +
* if you want to report same crash twice, you have to remove CC's DB (default path /tmp/CCDB) and make a crash again
 +
* if reporting causes an installation of many debuginfos, then a timeout on dbus can occur. In that case, try to report crash again after debuginfos are installed.
 +
* if crash-catcher daemon unexpectedly crashs, then look for .lock files in /var/cache/crash-catcher/ and delete them. They may cause a deadlock.
  
 
=== Test ===
 
=== Test ===

Revision as of 18:23, 25 February 2009

DATE TIME WHERE
Thu February 26, 2009 From 12:00 to 20:00 UTC (7am -> 3pm ET) #fedora-qa)

What to test?

Today's instalment of Fedora Test Day will focus on:

Who's available

The following cast of characters will be available for testing, workarounds, bug fixes, and general discussion ...

Prerequisite for Test Day

  • Rawhide or F10 fully updated (some tips below). Remember, Rawhide is an unsupported development branch: use an installation you don't mind getting broken
  • Selinux enabled. If you need to run in permissive mode please file a bug against selinux
Warning.png
no animals will be hurt during testing

How to test?

Update your machine to latest Rawhide or F10

See the instructions on the Rawhide page on the various ways in which you can install or update to Rawhide.

Installation

  1. Create a yum repo for crash-handler. For example, to create a repo called /etc/yum.repos.d/crash-handler.repo, type:
# cat <<EOF>>/etc/yum.repos.d/crash-handler.repo
[crash-handler]
name=crash-handler
baseurl=http://jmoskovc.fedorapeople.org/crashcatcher/
EOF
  1. Install the crash-catcher packages:
    # yum install crash-catcher*
  2. Restart the computer to launch the daemon and load the necessary dbus configuration files
  3. check if the daemon is really running, if not for some reason, run crash-catcher
  4. run cc-applet (as an ordinary user)

rpm are available at rpms

Configuration

after installation some default settings are stored in /etc/crash-catcher/* configuration is written on single line "key = value {, value}"

  • main config file is /etc/crash-catcher/crash-catcher.conf
  * OpenGPGPublicKeys list of GPG keys
  * EnableOpenGPG, check if a package is signed with one of keys
  * BlackList blacklisted backages
  * EnabledPlugins a list of enabled plugis. There should to be at least one language/application plugin and database plugin
  * Database denotes database plugin, there has to be one database plugin! (crash-catcher-plugin-sqlite3)
  * every language/application plugin can have several reporter plugins. If you want to report something, then it has to have at least one :-)
  • Plugins conf files are in /etc/crash-catcher/plugins/*
  * description of options is in these files.

Known issues

  • if you want to report same crash twice, you have to remove CC's DB (default path /tmp/CCDB) and make a crash again
  • if reporting causes an installation of many debuginfos, then a timeout on dbus can occur. In that case, try to report crash again after debuginfos are installed.
  • if crash-catcher daemon unexpectedly crashs, then look for .lock files in /var/cache/crash-catcher/ and delete them. They may cause a deadlock.

Test

Follow the test case.

Results

If you find any bug (i.e. the test case does not complete as expected, or you encounter some buggy behaviour while carrying it out), then file a ticket via the crash-catcher Trac system. Design discussion can also take place on the crash-catcher mailing list.

Please record what applications you test with crash-catcher and their results in the table below.

User Smolt Profile Application Tested Bug(s) Comment(s)
James Laska HW Package Install https://fedorahosted.org/crash-catcher/ticket/1 Can't install the packages (bad %requires)