Line 147: | Line 147: | ||
| https://fedorahosted.org/crash-catcher/ticket/22 | | https://fedorahosted.org/crash-catcher/ticket/22 | ||
| Wrong recognition of the content of the reported email | | Wrong recognition of the content of the reported email | ||
|- | |||
|- | |||
| [[User:rbiba|Radek Biba]] | |||
| [-] | |||
| | crash-catcher | |||
| https://fedorahosted.org/crash-catcher/ticket/23 | |||
| [RFE] default select the last package dump in the GUI list | |||
|- | |- | ||
|- | |- |
Revision as of 15:17, 26 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 ...
- Development - Zdenek Prikryl Jiri Moskovcak
- Quality Assurance - Martin Koci, Radek Biba, James Laska, Adam Williamson
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
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
- A yum repo is available to provide easy access to koji builds for F11 and F10. Run the following command to create the repo config file for crash-catcher:
# cat <<EOF>>/etc/yum.repos.d/crash-catcher.repo [crash-catcher] name=crash-catcher baseurl=http://jlaska.fedorapeople.org/repos/crash-catcher/\$releasever/\$basearch/ gpgcheck=0 EOF
- Next, install the crash-catcher packages:
# yum install crash-catcher\*
- Then restart the computer to launch the daemon and load the necessary dbus configuration files
- Check if the daemon is really running, if not for some reason, run crash-catcher
- Run cc-applet (as an ordinary user)
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 working config file /etc/crash-catcher/crash-catcher.conf
# test conf file. it will be generated in the future # Enable GPG check EnableOpenGPG = no # GPG keys OpenGPGPublicKeys = /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora # blacklisted packages BlackList = bash, bind, apache2 # enabled plugins EnabledPlugins = SQLite3, CCpp, Mailx, Logger # selected DB plugin Database = SQLite3 # reporters association CCpp = Mailx, Logger
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 dbus timeout may 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.
- if it seems to do nothing, try to disable PGP checking and restart daemon
- gui writes some gtk warnings
- report editing from gui doesn't work
- it needs rpm >= 4.6.0-1 (rc3 segfaults)
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) |
Martin Koci | HW | Vim - Deadlock while creating the Lock | https://fedorahosted.org/crash-catcher/ticket/4 | Can't catch the segmentation fault of the vim |
Martin Koci | HW | All | https://fedorahosted.org/crash-catcher/ticket/10 | SELinux is preventing mailx (sendmail_t) "read" to ./binary_data1 (var_t). |
Radek Biba | [-] | The security issue | https://fedorahosted.org/crash-catcher/ticket/5 | The temporary file /tmp/CCDB is a potentially security hole |
Radek Biba | [-] | crash-catcher | https://fedorahosted.org/crash-catcher/ticket/17 | The "Cancel" button works as the "Apply" button :) |
Radek Biba | [-] | crash-catcher | https://fedorahosted.org/crash-catcher/ticket/22 | Wrong recognition of the content of the reported email |
Radek Biba | [-] | crash-catcher | https://fedorahosted.org/crash-catcher/ticket/23 | [RFE] default select the last package dump in the GUI list |
Michal Schmidt | [-] | mc | https://fedorahosted.org/crash-catcher/ticket/6 | "Unable to get report! Debuginfo missing?" |
Petr Sklenar | [-] | all | https://fedorahosted.org/crash-catcher/ticket/15 | "crash-catcher-5 dead but subsys locked" |
David Kovalsky | HW | Package install | https://fedorahosted.org/crash-catcher/ticket/20 | cc-applet doesn't start |